mikko-skills
Skill0 starsChanged 5 months agoMITView on GitHub
List every installed `mikko-*` skill with a plain-English (barney) one-liner — for "what mikko skills do I have", "list my skills", "remind me what's installed", or onboarding a machine. Runs a bundled script (deterministic; reads each skill's `barney:` field, falls back to `description`). One-screen output. For dense per-skill detail use `/mikko-help`.
In this repository15 other files it gives its agents.
- ai-codegen-smell-auditSkill
- auditSkill
- dotnet-auditSkill
- llm-injection-auditSkill
- mikko-audit-suiteSkill
- mikko-helpSkill
- mikko-installSkill
- react-anti-patterns-auditSkill
- readme-drift-syncSkill
- security-auditSkill
- session-costSkill
- skill-calibrationSkill
- skills-freshnessSkill
- skills-qualitySkill
- skill-usageSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Run the bundled script and print its output verbatim:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
mikko-skills
Print every installed mikko-* skill with a barney-style one-liner — the friendly, scannable counterpart to mikko-help's denser table. Same deterministic work (glob + frontmatter parse), run as a script rather than LLM prose.
How to run
Run the bundled script and print its output verbatim:
python3 ~/.claude/skills/mikko-skills/mikko-skills.py(From the source repo: python3 skills/mikko-skills/mikko-skills.py.) It globs ~/.claude/skills/mikko-*/SKILL.md and the project-local .claude/skills/mikko-*/SKILL.md, reads each skill's barney: field (falling back to a truncated description, tagged (no barney yet)), dedupes with project-local winning, and prints a vertical name-then-one-liner list.
Why barney style
The description: field is written for Claude — dense, trigger-loaded. Barney is written for you: one or two punchy plain-English sentences so a scan of the list answers "which skill do I want right now?" without re-reading dense prose. When you add a new mikko-* skill, add a barney: field — one or two jargon-free sentences describing what it does and the outcome, not how.
Freshness check
Staleness checks run by /mikko-skills-freshness on any change to this skill.
[[check]]
kind = "file_contains"
path = "SKILL.md"
pattern = "^barney:"
[[check]]
kind = "file_contains"
path = "SKILL.md"
pattern = "mikko-\\*/SKILL\\.md"
[[check]]
kind = "path_exists"
path = "mikko-skills.py"Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.