Skills para-skill

📦

para-skill

Name: para-skill
Author: scifishelf

Content revision r1 Safe 🌐 Network access⚙️ External commands

Organize Notes with PARA

Notes lose value when projects, responsibilities, and references mix together. This skill classifies Obsidian notes into PARA categories and proposes safe routing, metadata, reviews, and archiving.

Supports: Claude Codex Code(CC)

🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "para-skill" from https://skillstore.io/skills/scifishelf-para-skill.md and its manifest at https://skillstore.io/api/skills/scifishelf-para-skill/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/scifishelf-para-skill.md Signed manifest GET /api/skills/scifishelf-para-skill/manifest Signed lockfile GET /api/skills/scifishelf-para-skill/lockfile

Test it

Using "para-skill". A meeting note about preparing the April leadership workshop, with action items and a deadline.

Expected outcome:

Classification: Project.
Confidence: high, because the note has a concrete outcome, deadline, and open tasks.
Recommended path: place it under the Projects folder after user confirmation.
Frontmatter recommendation: mark it active and set a near review date.

Using "para-skill". A collection of reading notes about React rendering patterns with no active tasks.

Expected outcome:

Classification: Resource.
Confidence: high, because the content is reference material without current action pressure.
Recommended path: keep it under Resources.
No archive action is recommended.

Using "para-skill". A project note marked done for more than 30 days, with no open tasks.

Expected outcome:

Classification: Archive candidate.
Confidence: medium until links and user intent are checked.
Recommended action: show a dry run and ask before moving the note.
Change log entry should be prepared if the move is approved.

Security Audit

Safe

v4 • 7/6/2026 Open versioned report

All 36 static findings were reviewed and adjudicated as false positives. The hardcoded URL is installation documentation, and the external command detections are markdown backticks or fenced examples. No prompt injection, data exfiltration intent, or malicious command behavior was found in the reviewed files.

Files scanned

810

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/scifishelf-para-skill/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/scifishelf-para-skill/security.svg)](https://skillstore.io/skills/scifishelf-para-skill?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/scifishelf-para-skill?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/scifishelf-para-skill/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/scifishelf-para-skill.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

scifishelf. (2026). para-skill security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/scifishelf-para-skill/audits/4

BibTeX citation

@techreport{scifishelf-scifishelf-para-skill-2026,
  author = {scifishelf},
  title = {para-skill security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/scifishelf-para-skill/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "para-skill security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "scifishelf"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/scifishelf-para-skill/audits/4"
identifiers:
  - type: other
    value: "skillstore:scifishelf-para-skill:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Process an Inbox Backlog

Classify unprocessed notes, propose target folders, and mark uncertain items for review.

Maintain a Team Knowledge Vault

Review project notes, recurring responsibility areas, and reference material for consistent PARA placement.

Prepare Safe Archiving Decisions

Identify completed or inactive notes and generate cautious archive recommendations before any move occurs.

Try These Prompts

Classify One Note

Classify this note using PARA. Explain the type, confidence level, supporting signals, and any missing information.

Route a Note Safely

Review this note and suggest the correct PARA folder. Show the current path, proposed path, confidence, and required confirmation.

Normalize PARA Metadata

Suggest PARA frontmatter for this note. Only include fields you can justify, and do not overwrite unrelated metadata.

Audit the Vault

Run a PARA hygiene audit for this vault. Prioritize inbox backlog, project next steps, stale areas, archive candidates, and review items.

Best Practices

Provide the current note path, title, frontmatter, and body when asking for classification.
Keep the skill in cautious mode when reviewing a large vault or unfamiliar folder structure.
Confirm any file move, archive action, or metadata update before applying changes.

Avoid

Do not classify notes by topic alone without checking action relevance.
Do not archive old notes only because they have not changed recently.
Do not ask it to replace specialized Obsidian tools for links, formatting, or file moves.