skill writer

Documentation Community

Skill notes

Core Workflow References

Open when you need to... · Read choose the minimum workflow path for create, update, iterate, or research-first work · references/mode-selection.md choose the simplest adequate execution shape before deciding files · references/execution-shapes.md apply writing constraints for depth, concision, and portability · references/design-principles.md decide what belongs in SKILL.md, references/, SPEC.md, or supporting files · references/reference-architecture.md

Artifact Layout References

Open when you need to... · Read keep the whole skill inline in one coherent SKILL.md · references/layout-inline-skill.md split optional deep knowledge into focused routed references · references/layout-reference-backed-skill.md add scripts for deterministic automation or validation · references/layout-script-backed-workflow.md define a skill that is usually invoked with explicit arguments · references/layout-argument-driven-skill.md

Workflow Mechanic References

Open when you need to... · Read break a task into fixed ordered steps · references/workflow-prompt-chaining.md classify requests and route them to different downstream paths · references/workflow-routing.md split independent work into parallel units or votes · references/workflow-parallel.md discover work units dynamically and coordinate worker outputs · references/workflow-orchestrator-workers.md

Claude Code References

Open when you need to... · Read use Claude-specific frontmatter or invocation controls · references/claude-frontmatter-invocation.md use Claude argument fields or substitution variables · references/claude-argument-substitutions.md build a skill that runs in isolated context: fork · references/claude-subagent-fork.md build a skill that uses Claude hooks for deterministic enforcement · references/claude-hook-backed.md

Example Profiles

Open when you need to... · Read see the expected depth for a documentation-heavy skill · references/example-documentation-skill.md see the expected depth for a workflow-process skill · references/example-workflow-process-skill.md see what a good routed skill looks like · references/example-router-skill.md see what a good subagent-fork skill looks like · references/example-subagent-fork-skill.md

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Documentation
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
@getsentry · 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
  • Shell exec
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-writer-getsentry.preview
# Step 3: Run iteration first when improving from outcomes/examples

1. Capture and anonymize examples with provenance.
2. Read `references/iteration-evidence.md` when examples should persist beyond the current turn.
3. Review skill behavior against working and holdout slices.
4. Propose improvements from positive/negative/fix evidence.
5. Carry concrete behavior deltas into authoring.

Discussion

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