skillify

Other Community v1.1.0

Skill notes

Contract

A feature is "properly skilled" when all 11 checklist items pass. Item 3 (cross-modal eval) is informational in v1.1.0 — it does not gate the skillpack-check audit, but a missing or stale receipt is surfaced so the user knows where the gate stands.

Phase 0: Should This Be a Skill?

Before skillifying, check: Will this be invoked 2+ times? (One-off work ≠ skill) Is there >20 lines of logic? (Trivial helpers don't need full infrastructure) Does it have a clear trigger phrase a user would actually say? If no to all three, it's a script, not a skill. Move on.

SKILL.md frontmatter template (copy-paste):

Body must include: Contract (what it guarantees), Phases (step-by-step), Output Format (what it produces). Extract deterministic code into scripts/*.ts.

Why this comes before tests

Tests lock in behavior. If the behavior is mediocre, tests lock in mediocrity. Cross-modal eval proves the quality bar FIRST, then tests cement it.

Step 1: Pick a representative input

Choose the input that exercises the skill's hardest documented use case. If unsure: use the primary trigger example from SKILL.md, or the most complex real-world input from the last 7 days of memory files.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@garrytan · v1.1.0 · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Required · OpenAI / Anthropic
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

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

Output preview skillify-garrytan.preview
# Step 2: Run the skill, capture output

Run the skill on the representative input. The OUTPUT FILE is what gets evaluated.

Discussion

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