Rethinking Prompt Assets
Rethink a set of prompt assets from zero — memory files (CLAUDE.md, AGENTS.md), skills, sub-agent definitions, and the flows they form — and propose large changes: delete, merge, split, rebuild, reroute. A sub-agent blind to the current assets designs the ideal set for the jobs they serve; the current set is compared with it and with usage evidence from transcripts. Finds what a one-file review cannot: overlap and contradiction between skills, unclear ownership, skills unused or never firing, delegation that drifted from the model-assignment source, flows with wasted stages or ill-fitting agen
Install
/plugin marketplace add tomada1114/tomada-claude-pluginsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add tomada1114/tomada-claude-plugins --skill rethinking-prompt-assetsgit clone --depth 1 https://github.com/tomada1114/tomada-claude-plugins.git /tmp/tomada-claude-plugins
mkdir -p ~/.claude/skills
cp -r /tmp/tomada-claude-plugins/tomada-kit/skills/rethinking-prompt-assets ~/.claude/skills/rethinking-prompt-assetsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Rethinking prompt assets Asked to review a set of skills, a model reads them one at a time and proposes edits to each. That review takes the current layout as given, so it never asks whether a skill should exist, cannot see what two skills say between them, and has no evidence of what is used. This skill reverses the order: jobs first, an independent design second, the current assets third. Deleting, merging and rebuilding are ordinary outcomes, and so is "the current shape is right": every asset gets a verdict, and a change has to show the cost of leaving things as they are. The existing single-purpose reviewers are parts, called where a step needs them: `auditing-prompt-docs` (wording and its linter), `creating-agent-skills` (one skill's structure; building a replacement), `auditing-repositories` (a repository's harness). Their own procedures, approval stops and remote writes do not run here; this skill's proposal is the only approval. Load one with the `Skill` tool; how to call each: [references/claude-code.md](references/claude-code.md#parts-and-their-own-side-effects). ## Contract **Input:** free-form. The scope is one of: | Given | Scope | |---|---| | nothing | The whole user-level estate: memory files, every skill and command, every sub-agent definition | | asset names | Those assets. Assets they name, or that name them, are context |
Details
- Skill name
rethinking-prompt-assets- Repository
- tomada1114/tomada-claude-plugins
- Path
tomada-kit/skills/rethinking-prompt-assets/SKILL.md- Repo updated
- 12 November 2026
FAQ
What does the Rethinking Prompt Assets skill do?
Rethink a set of prompt assets from zero — memory files (CLAUDE.md, AGENTS.md), skills, sub-agent definitions, and the flows they form — and propose large changes: delete, merge, split, rebuild, reroute. A sub-agent blind to the current assets designs the ideal set for the jobs they serve; the current set is compared with it and with usage evidence from transcripts. Finds what a one-file review cannot: overlap and contradiction between skills, unclear ownership, skills unused or never firing, delegation that drifted from the model-assignment source, flows with wasted stages or ill-fitting agen
How do I install the Rethinking Prompt Assets skill?
Claude Code plugin: /plugin marketplace add tomada1114/tomada-claude-plugins. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Rethinking Prompt Assets popular?
It lives in tomada1114/tomada-claude-plugins, which has 5 GitHub stars and 0 forks.
Related skills
Auditing Prompt Docs
5tomada1114/tomada-claude-plugins
Audit and fix prompt-bearing documents — SKILL.md, CLAUDE.md, AGENTS.md, agent and command definitions, reference files, whole repositories — against Anthropic's published prompting guidance for current Claude models, proposing edits for approval before writing anything. Also answers how to prompt a specific model: holds the per- model guidance for Claude Fable 5.2, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 alongside the cross-model practices. Use when reviewing or slimming an instruction file, when instructions are ignored or fire too often, when migrating a prompt to a newer m
Auditing Repositories
5tomada1114/tomada-claude-plugins
Audit the repository you are in, often a template or an app cut from one, for technical debt and room to improve in four areas: architecture and design patterns; tests; file structure and code quality; and tooling, CI, dependencies and the agent harness. Design a safe, test-first fix for every evidenced finding, and file the findings as GitHub issues that follow the repository's own issue conventions (triaging-issues, issue forms, past issues). A finding inherited from the template is also filed in the template repository. Cheap read-only sub-agents collect the evidence and high-effort analyst
Authoring Goal Prompts
5tomada1114/tomada-claude-plugins
Author a self-contained prompt for Claude Code's /goal command, run unattended in a separate session — a lead-to-staff handoff where this session researches, designs, and decides with full context, and a fresh executor session (Opus 5.5 or Fable 5.2, with none of that context) implements. Drafts a goal with measurable done-criteria, transcript-verifiable checks, scope + anti-cheat constraints, and stop rules; packages design intent, code examples, research findings, checklists, and pre-answered decisions as support files in a per-goal state directory whenever the executor would otherwise re-de
Syncing Agent Tiers
5tomada1114/tomada-claude-plugins
Push the canonical sub-agent tier definitions (executor, architect, scout, worker) into every listed repository's .claude/agents/ and .codex/agents/, opening one auto-merging PR per repository. Use after changing a tier's model or effort, when adding a repository to the sync list, or as the last step of distributing-plugins.
Refining Prompts
5tomada1114/tomada-claude-plugins
Polish a rough instruction (often dictated by voice) into a precise prompt that can be handed straight to another agentic coding session (Claude Code, Codex CLI, etc.), and print it in the CLI as a single code block (no file is saved). Runs a light scouting pass only when needed, and questions the user only when needed; the investigating and the thinking are deliberately left as work for the receiving session. When the user wants a /goal prompt for an unattended run, use authoring-goal-prompts instead. Use when asked to write, tidy up, or sharpen a prompt to hand to another session.
AI Company Search
9Lord1Egypt/RA-Skills
Search artificialintelligencecompanies.com to find AI vendors and startups serving a given niche or addressing a given problem, returning name, canonical URL, and description per match via the site's public JSON API and JSON-LD category pages.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.