toclaude

43 stars

byagenticnotetaking

View on GitHub Installation ↓

Best use case

toclaude is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Teams using toclaude 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

$curl -o ~/.claude/skills/toclaude/SKILL.md --create-dirs "https://raw.githubusercontent.com/agenticnotetaking/eidos/main/skills/toclaude/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/toclaude/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How toclaude Compares

Feature / Agent	toclaude	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:toclaude

Update CLAUDE.md or specs to correct undesired behaviour.

## Usage

```
/eidos:toclaude [description of correction]
```

## Instructions

1. Understand the correction — what went wrong, what should happen instead
2. Identify the right location:
   - **`inject/core.md`** — plugin rules that apply to all eidos projects
   - **`inject/feature/*.md`** — rules tied to a config-gated feature
   - **CLAUDE.md** — project-specific rules (not plugin-wide)
   - **Specific spec** — scoped rules that apply to one area
   - **New claim in `eidos/`** — if the correction is a general principle
3. If adding to context files: include an actionable TL;DR inline, not just a link to a spec. Context should be self-sufficient for 90% of work.
4. Draft the addition or modification
5. Present for approval (per [[c - agency in implementation not direction - surface reasoning for human steering]])
6. Write the change and commit

## Output

- Modifies: CLAUDE.md or relevant spec/claim file

Related Skills

spec

from agenticnotetaking/eidos

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.

Development Planning & Specs