Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From techne
Scaffolds new techne skills by providing an authoring template, quality criteria, and structural guidance. Use when starting a new SKILL.md.
npx claudepluginhub lynxlangya/techne --plugin techneHow this skill is triggered — by the user, by Claude, or both
Slash command
/techne:_templateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this file as the starting point for a new techne skill. Keep the skill body
Meta-skill that generates and refines SKILL.md files using the 12 prompting techniques as a quality checklist. The skill that writes skills. Triggers: craft skill, create skill, generate skill, write skill, skill template, meta prompt, improve skill, refine skill.
Defines structure, size budget, description format, and review checklist for creating or modifying skills in the plugin.
Generates structured SKILL.md files for new Claude Code skills from purpose descriptions, following templates with frontmatter, usage triggers, steps, and best practices.
Share bugs, ideas, or general feedback.
Use this file as the starting point for a new techne skill. Keep the skill body tool-neutral: the guidance here should make sense outside any one host, with tool-specific loading handled by plugin manifests.
A techne skill must force a move the model can make but often skips. It is not a place to restate common knowledge, collect vague advice, or duplicate what the platform or superpowers already handles well.
Before authoring, identify:
State the triggering situation in concrete terms. Prefer user intents, task conditions, and failure signals over broad domain labels.
Write the smallest set of instructions that reliably forces the move. Use direct commands, checks, and stop conditions. Avoid product-specific paths, local tool names, or host-only features unless they are documented as optional references.
Each real skill should include an eval.md alongside SKILL.md. The eval file
records the empirical acceptance test from WORKFLOW.md: baseline behavior,
with-skill behavior, what counts as improvement, and the pass bar.
For scaffold-only or template changes, direct mechanical validation is enough.
Optional files live next to SKILL.md when they remove noise from the main
skill:
eval.md for the empirical acceptance test.scripts/ for executable helpers the model may run.reference.md for longer material loaded only when needed.Do not add empty support folders. Add them only when the skill actually needs them.