skill creation walkthrough

Security Community

Skill notes

When to use

You catch yourself writing the same prompt or instructions repeatedly. You want to package a workflow or framework for reuse. An existing skill of yours is not triggering when it should. You are publishing skills for others to use. You want to teach Claude a domain-specific way of working.

When NOT to use

For one-off prompts (just write the prompt). For information that should live in system context, not progressive disclosure. For changing Claude's general behavior across all conversations (use Claude.ai settings or system prompts, not skills). For replacing tool calls (skills are instructions, not tools).

Required inputs

The task or workflow you want to encode. The audience: who will trigger this skill, in what kind of conversation. Existing artifacts: prompts you have used, docs you have written, examples of good output.

The framework: how skills work

A Skill is a folder with a SKILL.md file. The SKILL.md has YAML frontmatter (name and description) and a body with instructions. It can also include reference files, scripts, or templates that get loaded when needed. The key property: progressive disclosure. Claude does not read every skill on every turn. The skill description lives in the system prompt. The SKILL.md body and references load only when the skill is triggered. This is what lets a user have hundreds of skills without polluting context.

Phase 1: Decide if a skill is the right shape

Not everything should be a skill. Run this test: Sign it should be a skill · Sign it should not be You repeat the same workflow 5+ times. · You used it once. The output benefits from a consistent structure. · Each output is bespoke. The task has a clear trigger (a question shape, a file type, a domain). · The task is part of every conversation already.

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
@rampstackco · no license declared
Token usage
Moderate
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
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

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

Output preview skill-creation-walkthrough.preview
# Deep dive: worked example

Imagine you keep writing technical post-mortem documents and want to skill-ify it. **Step 1: Decide it's a skill.** You write 5+ post-mortems a year, output benefits from consistency, others on the team would use it. Yes, build a skill. **Step 2: Trigger.** "When the user wants to write a post-mortem, retrospective, or after-action report. When an incident has happened and we are reviewing what went wrong." **Step 3: Description.** > "Write a structured post-mortem after an incident, outage, or significant project failure. Use when the user mentions post-mortem, retrospective, after-action rep

Discussion

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