core

Plugin core from marketplace skills in baleen37/skills. Commands read from the repo's manifest — yesterday.

Skills (38)

• ask

  Ask which skill or flow fits your situation. A router over the skills in this repo.

• browser

  Read when you need browser automation (QA, element interaction, screenshots, network capture, recording), or work in the user's logged-in accounts and apps (e.g. Slack, X, LinkedIn) through their real browser.

• build-eval

  Build a runnable eval set for one flow of an LLM-powered app. Use when the user wants to measure whether their LLM app works, asks "how do I know if my change helped", or is about to change a prompt, model, or tool and needs a baseline number.

• code-review

  Review the current diff, or a PR number/branch/path target, for correctness bugs plus reuse/simplification/efficiency/altitude/conventions cleanups in one careful pass. Pass --comment to post findings as inline PR comments, or --fix to apply the findings to the working tree after the review. Use whe

• codebase-design

  Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

• competitive-agents

  Use when designing systems, architectures, or APIs, when multiple valid approaches exist with no single obvious answer, or when user explicitly requests parallel/competing solutions

• create-pr

  Create PR — commit, push, PR, wait for merge.

• diagnosing-bugs

  Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

• domain-modeling

  Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

• e2e-scenario-testing

  Use when verifying a running application end-to-end through its real interface — a web UI, a CLI, or a TUI — by writing and executing agent-run "scenario cards" against a freshly built instance with falsifiable assertions. Trigger on "test it end to end", "prove the UI actually works", "write/run a

• grill-me

  A relentless interview to sharpen a plan or design.

• grill-with-docs

  A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

• grilling

  Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

• handoff

  Compact the current conversation into a handoff document for another agent to pick up.

• hillclimb

  Iteratively improve an LLM-powered app against an existing eval with a train/test split. Use when the user says "hillclimb", wants to raise an eval score, tune a prompt or tool descriptions against an eval, or cut cost or latency while holding quality.

• implement

  Implement a piece of work based on a spec or set of tickets.

• improve-codebase-architecture

  Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

• jira-to-todo

  내 Jira 잔여 이슈를 오늘의 Obsidian Daily 노트 TODO 섹션에 추가하고, 노트에 이미 있는 Jira 항목의 상태와 새 하위 이슈를 동기화합니다.

• learn

  Teach the user a new skill or concept over several sessions, in a workspace under `~/.skills/learn/`.

• prototype

  Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• research

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

• retro

  Conduct a retrospective on a coding session.

• setup

  Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

• ship

  Use when preparing to deploy to production, asked to "ship", "release", or "deploy", or when you need to verify a deploy succeeded or plan a rollback. Covers the full flow: pre-deploy checks, the deploy itself, and post-deploy verification with rollback on failure.

• simplify

  Review the changed code for reuse, simplification, efficiency, and altitude cleanups, then apply the fixes. Quality only — it does not hunt for bugs; use core:code-review for that. Use when the user asks to simplify, clean up, or tidy the current diff without changing behavior.

• tdd

  Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

• to-inbox

  Obsidian Inbox에 사용자가 고른 아이디어나 배운 점을 노트로 저장합니다.

• to-questionnaire

  Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

• to-rfcs

  Use when writing, reviewing, or improving RFCs, requests for comments, technical design docs, architecture proposals, engineering decision records, API proposals, migration plans, or cross-team technical decisions.

• to-spec

  Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

• to-tickets

  Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

• to-todo

  사용자가 지정한 할 일을 오늘의 Obsidian Daily 노트 TODO 섹션에 체크박스로 추가합니다.

• triage

  Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

• verify

  Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck. Run before committing nontrivial changes, or when asked to "verify this", "qa", or "does this work?"; bootstraps this repo's projec

• wait-what

  Stop. That last message did not land: re-pitch it.

• wayfinder

  Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

• wizard

  Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can pe

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Subagents (1)

• researcher

  Use this agent to find and verify external reference material from official documentation, APIs, registries, standards, papers, releases, GitHub sources, and reputable web sources. Do not use for codebase exploration or local bug investigation.

Hooks (7)

• WorktreeCreate

  bash "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/setup-worktree.sh"

• PreToolUse

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/commit-guard.sh"

• SessionStart

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

• UserPromptSubmit

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

• PermissionRequest

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

• Stop

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

• SessionEnd

  "${PLUGIN_ROOT:-$CLAUDE_PLUGIN_ROOT}/hooks/agent-status.sh"

Similar plugins