tools
This Claude Code skill manages persistent, reusable procedures by creating, updating, or deleting skill files stored in an isolated directory. Use it to codify repeatable workflows like setup sequences, debugging recipes, or project-specific processes that should be available across future sessions while remaining separate from manually authored skills.
git clone --depth 1 https://github.com/can1357/oh-my-pi /tmp/tools && cp -r /tmp/tools/packages/coding-agent/src/prompts/tools/manage- ~/.claude/skills/toolsmanage-skill.md
Managed skill: `SKILL.md` in isolated `~/.omp/agent/managed-skills`; surfaced as a normal skill in future sessions. Use: repeatable procedures worth codifying — setup sequence, debugging recipe, project-specific workflow. User-authored skills separate; tool NEVER edits them. - `action: "create"` — fails if skill exists. - `action: "update"` — overwrites body; fails if skill absent. - `action: "delete"` — fails if skill absent. `name`: kebab-case (lowercase letters, digits, hyphens). `description`: specific; drives discovery. No frontmatter in `body`; generated from `name` and `description`.
Re-encode verbose prose into a dense telegraphic register — punctuation as connectives, label frames, verbless assertions — without losing normativity or precision. Use when compressing system prompts, tool/function descriptions, skill bodies, or agent instructions; reducing token count or context bloat; making documentation token-efficient for LLM input; or rewriting text in compressed notation.
Write system prompts, tool docs, and agent definitions. Project tag conventions + RFC 2119 keywords + dense compression. Use when authoring or editing any prompt the model reads.
Optimize the description prompts an AI agent reads to learn its built-in tools (the `.md` files under prompts/tools/). Two halves: (1) measure how much of a prompt is already inferable from the tool's JSON parameter schema + name, to prune redundancy with evidence; (2) house authoring rules for what belongs in a tool prompt vs what stays in code. Use when auditing, trimming, writing, or reviewing tool prompts, deciding what schema field descriptions already cover, or testing schema-vs-prompt overlap before deleting prompt lines.