skill review

Security Community

Skill notes

Step 1: Load Target ⚠️ REQUIRED

Identify the skill to review. Accept: Explicit path: /skill-review path/to/skill Current directory context: if user is already in a skill folder Skill name: search within the workspace for matching skill directory Read the full SKILL.md and list all files in the skill directory. Count SKILL.md line count — this is a key metric.

Step 2: Analyze ⚠️ REQUIRED

Load references/review-criteria.md for detailed criteria. Evaluate the skill across five dimensions:

2.1 Structure Compliance

Questions to answer: Does the directory follow the standard layout (SKILL.md, scripts/, references/, assets/)? Is SKILL.md under 500 lines? Does frontmatter contain only name and description (plus optional allowed-tools, license, metadata)? Are there unnecessary files (README.md, CHANGELOG.md, LICENSE duplicates)?

2.2 Description Quality

Questions to answer: Does the description include concrete trigger keywords and phrases? Does it use keyword bombing (multiple phrasings of the same intent)? Is it self-contained — can a router understand what this skill does without reading the body? Does it avoid putting "When to Use" info in the body instead of the description?

2.3 Workflow Design

Questions to answer: Is there a trackable checklist with copy-paste-friendly format? Are critical steps marked with ⚠️ REQUIRED or ⛔ BLOCKING? Are there confirmation gates before destructive/generative operations? Is the workflow linear and progressive, or does it jump around?

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@sanyuan0704 · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Load Target ⚠️ REQUIRED

Identify the skill to review. Accept: Explicit path: `/skill-review path/to/skill` Current directory context: if user is already in a skill folder Skill name: search within the workspace for matching skill directory Read the full SKILL.md and list all files in the skill directory. Count SKILL.md line count — this is a key metric.

02
Step 2: Analyze ⚠️ REQUIRED

Load references/review-criteria.md for detailed criteria. Evaluate the skill across five dimensions:

03
Step 3: Report ⚠️ REQUIRED

Step 3: Report ⚠️ REQUIRED

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.