Best use case
toskill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Teams using toskill should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/toskill/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How toskill Compares
| Feature / Agent | toskill | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill provides specific capabilities for your AI agent. See the About section for full details.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# /eidos:toskill Turn a discovered pattern into a reusable skill. ## Usage ``` /eidos:toskill [name] ``` ## Instructions 1. If no name provided, ask what the skill should do 2. Extract the pattern from conversation 3. Create `skills/<name>/<name>.md` with: - tldr in frontmatter - Skill heading with `# /eidos:<name>` - Usage section - Instructions section - Output section 4. Create `skills/<name>/SKILL.md` symlink → `<name>.md` 5. Create spec in `eidos/skills/spec - <name> skill - <claim>.md` (every skill gets a spec) 6. Commit all files ## Output - Creates: `skills/<name>/<name>.md` + SKILL.md symlink - Creates: `eidos/skills/spec - <name> skill - <claim>.md`
Related Skills
spec
This skill guides an AI agent to collaboratively think through and create a detailed technical specification document via structured Q&A. It clarifies target, behavior, and design before generating the spec file.
worktree
No description provided.
wish
No description provided.
weave
No description provided.
video
No description provided.
true-name
No description provided.
toscript
No description provided.
tomd
No description provided.
toeidos
No description provided.
todo
No description provided.
toclaude
No description provided.
tldr
No description provided.