skill-creator-linter
Internal tool (not user-invocable). Called by meta-skill-creator as a DAG step (kind: agent) to lint a candidate meta-skill SKILL.md against G1 (parse + reference check + xml_escape grep + structural lint) and G2 (scheduler dry-run with stub executors). Deterministic, sub-second, no LLM. Returns JSON diagnostics.
Profile →npx skills add opensquilla/opensquilla --skill skill-creator-linter --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skill Creator Linter Validates a candidate meta-skill SKILL.md before it gets registered. ## G1 rules | Rule | Check | |---|---| | G1.1 | `parse_meta_plan` does not raise | | G1.2 | Every `step.skill` for kind=agent/skill_exec exists in the main catalog | | G1.3 | Template variables resolve at render time (covered by G1.1) | | G1.4 | `on_failure` parser rules (covered by G1.1) | | G1.5 | step `kind:` consistency (covered by G1.1) | | G1.6 | Grep: every `{{ inputs.user_message | xml_escape` usage must have `xml_escape` (or `slugify`) as the first filter. Violations are reported as G1 errors (block linter). | ## G2 dry-run Replace step executors with stubs yielding `_StepDone(text="<stub:id>")`. Run scheduler; pass if no exception and topology terminates. ## Usage ``` uv run python {baseDir}/scripts/lint.py --skill-md path/to/SKILL.md --gates G1,G2 uv run python {baseDir}/scripts/lint.py --skill-md-stdin --gates G1,G2 < SKILL.md ``` ## Output JSON to stdout: `{"G1": {"passed": bool, "diagnostics": [...]}, "G2": {...}}`. ## Fallback Manually inspect SKILL.md and run `parse_meta_plan` in a Python REPL.
- G1 rules
- G2 dry-run
- Usage
- Output
- Fallback
What does the skill-creator-linter skill do?
Internal tool (not user-invocable). Called by meta-skill-creator as a DAG step (kind: agent) to lint a candidate meta-skill SKILL.md against G1 (parse + reference check + xml_escape grep + structural lint) and G2 (scheduler dry-run with stub executors). Deterministic, sub-second, no LLM. Returns JSON diagnostics.
How do I install it?
Run `npx skills add opensquilla/opensquilla --skill skill-creator-linter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From opensquilla/opensquilla, a repository with 6,515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.