skill architect

Design Community

Skill notes

Core Philosophy

Understand before building. Never generate a SKILL.md until you've completed Discovery and Architecture phases. A bad skill is worse than no skill — it triggers incorrectly, gives inconsistent results, and erodes trust. Progressive disclosure is everything. The three-level system (frontmatter → SKILL.md body → linked files) exists for a reason: token economy. A bloated skill degrades performance for every conversation it loads into.

Workflow Overview

Move through phases sequentially. Never skip Discovery. Each phase has explicit exit criteria before you advance.

Phase 1: Discovery

Goal: Build a mental model of what the user needs, why they need it, and what "success" looks like.

1.1 — Understand the Problem

Start by asking about the OUTCOME, not the implementation. Key questions (ask conversationally, not as a checklist dump): What workflow do you want to make consistent? Get a concrete example of what they do today, step by step. What goes wrong without the skill? Understand the pain: inconsistency,

1.2 — Define Use Cases

Nail down 2-3 concrete use cases. For each, capture: If the user is vague, give them examples to react to. It's easier to refine a concrete proposal than to articulate needs from scratch.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tech-leads-club · CC-BY-4.0
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.

01
Phase 1: Discovery

Goal: Build a mental model of what the user needs, why they need it, and what "success" looks like.

02
Phase 2: Architecture

Goal: Make structural decisions before writing a single line of the skill.

03
Phase 3: Craft

Goal: Write the skill with precision.

04
Phase 4: Validate

Goal: Verify the skill before delivery.

05
Phase 5: Deliver

Goal: Package and present the completed skill.

Discussion

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