By WellDunDun
Public Builder skills for efficient frontier-model orchestration, clear status recaps, and Agent-Native Plan workflows.
Use when running Claude Fable on codebase-heavy or token-heavy work and the user wants Fable to orchestrate research, coding, and testing while cheaper subagents do bounded heavy lifting.
Apply the same orchestration as `/efficient-fable` to any high-cost frontier model: delegate research, coding, and testing to cheaper subagents while keeping planning, synthesis, and final review with the expensive model.
Use when adding or following the red/yellow/green final status block convention for agent responses, especially by installing managed AGENTS.md or CLAUDE.md instructions.
Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.
Use Agent-Native Plans when coding-agent work needs a reviewable plan published as an interactive document ā inline diagrams, annotated code walkthroughs, file trees, optional UI wireframes or prototypes, open-question forms, and comments ā before implementation starts.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Small, composable skills for coding agents.
These skills are for teams that want the agent to stay sharp where judgment matters: orchestration, review, planning, validation, and clear communication. They are not a giant process framework. Install the pieces you want, adapt them to your project, and let the model keep room to think.
/efficient-fableUse Claude Fable as the orchestrator, architect, synthesizer, and final judge while lighter agents handle token-heavy research, coding, testing, and log reduction.
Solves for expensive-model waste: Fable should spend tokens on judgment, not on reading every file, reducing every log, or manually running every browser check.
/efficient-frontierApply the same orchestration as /efficient-fable to any high-cost frontier
model: preserve the expensive model for planning, tradeoffs, integration,
validation strategy, and final review; use cheaper agents for bounded heavy
lifting.
Solves for broad work that can be parallelized without asking the most expensive model to do every scan and every edit itself.
/stay-within-limitsCheck current 5-hour and weekly usage before substantial work and between parallel waves, then pause new execution at 95% until the active window is clear enough to continue.
Solves for long-running agent sessions that accidentally exhaust the current budget window mid-task instead of pausing cleanly and resuming with a self-contained plan.
/visual-planTurn risky plans into human-optimized MDX documents with custom visual blocks: diagrams, wireframes, prototypes, visual schema maps, OpenAPI-style API specs, annotated code, open questions, and review comments.
Solves for plans that are too important to bury in chat. The output is scannable, commentable, and intuitive enough for a human to approve before code changes start.
/visual-recapTurn a branch, commit, or PR diff into a human-optimized visual recap with MDX and custom components: annotated diffs, diagrams, API diffs, visual schema maps, file maps, and UI state summaries.
Solves for diffs that hide the shape of the change. Reviewers can understand contracts, architecture moves, schema changes, and UI impact before diving into raw line-by-line review.
/quick-recapAdd a concise final status block convention so every completed response ends with a clear green, yellow, or red work-state signal.
Solves for ambiguity at the end of agent work: done, pending a specific non-routine step, or blocked on the user.
Example green status:
š¢ Updated quick recap docs with output examples
Example yellow status:
š” Code updated, set PROVIDER_WEBHOOK_SECRET before testing webhooks
Run the installer:
npx @agent-native/skills add
The installer walks you through the choices:
AGENTS.md / CLAUDE.md instruction blocks when the
selected skills have always-on guidance./visual-recap is
selected.Skip the picker with --skill:
npx @agent-native/skills add --skill quick-recap
npx @agent-native/skills add --skill visual-recap --with-github-action
You can also use Vercel's skills CLI for a plain skill-folder copy:
npx skills add BuilderIO/skills --skill quick-recap
That installer is useful for quick copying, but it does not add the managed
AGENTS.md / CLAUDE.md instruction blocks or the PR Visual Recap GitHub
Action that pair well with these skills.
Frontier orchestration runtime for delegating work across harnesses, models, and providers.
No description provided.
Detects a canary word in assistant replies and prompts session compaction.
npx claudepluginhub welldundun/frontier-builderio-skills-forkA growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC plugin for engineering teams - 67 agents, 278 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
Plugin-safe Claude Code distribution of Agentic Awesome Skills with 1,913 supported skills.
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,884 supported skills.
Matt Pocock's agent skills for real engineering ā grilling, spec/ticket flows, TDD, code review, domain modelling and more. Plug-and-play, not vibe coding.