agent-skills

Plugin agent-skills from marketplace m0r6an-agent-skills in m0r6aN/agent-skills. Commands read from the repo's manifest — 7 days ago.

Skills (43)

• synced

  Inspect and maintain the synced skill snapshot under skills/synced - the versioned bucket the skill-sync tooling writes when it mirrors installed skills into this repository. Use when reconciling or reviewing that mirror, comparing a captured copy against its source skill, or investigating snapshot

• accomplish

  Turns a vague objective into a verifiable goal, then orchestrates the cheapest way to reach it under guardrails — a direct action, a guarded work loop, periodic checks via /loop, or a delegation chain across the lifecycle skills. Interviews one question at a time to pin the outcome, verification, bo

• api-and-interface-design

  Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

• browser-testing-with-devtools

  Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MC

• ci-cd-and-automation

  Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

• code-review-and-quality

  Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

• code-simplification

  Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

• constraint-driven-development

  Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-i

• context-engineering

  Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

• debugging-and-error-recovery

  Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when something that worked before stopped working — a passing test that starts failing, a regression after a code change — and you need to find w

• deprecation-and-migration

  Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to

• documentation-and-adrs

  Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

• doubt-driven-development

  Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be che

• frontend-ui-engineering

  Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-gene

• get-app-specs

  Extract a canonical application specification from a codebase — features, business rules, requirements, domain canon, and dependencies — each evidence-backed, confidence-labeled, and liveness-checked (does this code actually get triggered?), with open questions surfaced. Use when taking a standalone

• git-workflow-and-versioning

  Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic

• go-live-readiness

  Orchestrates a complete go-live readiness assessment for an existing system by sequencing initiative-coordination as the control plane, invoking security-review for security-sensitive surfaces, and dispatching parcel-driven-development only for remediation work surfaced by failed gates or scenarios.

• idea-refine

  Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine th

• incremental-implementation

  Implements multi-file features as thin, independently verifiable slices, including feature-flagged rollouts. Use when changing more than one file, writing a large amount at once, or a task feels too big to land in one step.

• initiative-coordination

  Coordinates multi-agent, multi-session, multi-project initiatives across repositories, services, applications, environments, integration boundaries, release gates, and persisted operational state. Use when a product effort spans multiple repos or services, requires end-to-end integration validation,

• interview-me

  Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invo

• lumber-jack

  Recovers leftover, stale, or abandoned git worktrees: rescues uncommitted changes and unpushed code stranded in a worktree as pull requests against the dev branch, then deletes the recovered worktrees and branches so only the base repo and the main branch remain locally. Use when a repo has leftover

• melt-faces

  Performs a blunt, evidence-backed premium and enterprise-grade teardown of one or more products (websites, web apps, dashboards, plugins, CLIs), judged against the top 1% of software. Covers UI, UX, information architecture, accessibility, performance, trust, enterprise governance, onboarding, and A

• modernize

  Contract-first modernization workflow for rebuilding legacy systems with provable behavioral equivalence. Use when a team needs to extract requirements and contracts, perform human validation, implement an idiomatic target solution, and verify parity with reconciliation reports and replayable receip

• observability-and-instrumentation

  Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the availabl

• parcel-compiler

  Develop, inspect, and verify the proof-gated Parcel Compiler scaffold and its frozen command contracts. Use when extending pcc, reviewing its canonicalization or Git utilities, or preparing a parcel that implements one of its currently stubbed commands. Do not use it as an operational compiler yet b

• performance-optimization

  Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

• planning-and-task-breakdown

  Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

• security-and-hardening

  Build-time secure-coding guardrails. Use while writing or changing code that handles user input, authentication, sessions, secrets, personal data, external integrations, new dependencies, or LLM/tool calls. For reviewing, auditing, or threat-modeling existing code or systems, use security-review ins

• security-review

  Perform a defensive technical security review of code, configs, containers, IaC, live services, or agentic AI systems. Use when the user asks to review, audit, check, harden, assess, or threat-model the security of a repo, file, Dockerfile, Kubernetes manifest, Terraform/Pulumi/Bicep stack, API, dep

• shipping-and-launch

  Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

• source-driven-development

  Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

• spec-driven-development

  Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when you need to draft a PRD-style spec stating the objective, boundaries, and success criteria for a project. Use when requirements are unclear, ambiguous, or only exist

• built-in-browser

  Read this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or \"your own browser\"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app an

• chrome-browser

  Read this skill before the first step that uses Claude in Chrome, the browser extension whose tools are named mcp__claude-in-chrome__* (also called Chrome, the browser extension, or the external browser) and which acts in the person's real Chrome with their own sign-ins; before those tools are turne

• computer-use

  Read this skill before the first step of any request to do something in an app on the person's own computer (Notes, Finder, System Settings, any desktop app), to look at their screen, or for \"computer use\". Computer use (desktop control) lets Claude take screenshots of the person's desktop and con

• deep-research

  Use this skill when the user's prompt requires (1) researching a topic across multiple sources, comparing options or alternatives, analyzing trends or history, understanding markets or industries, or reviewing literature or studies and (2) synthesizing that research into a comprehensive, narrative r

• docs

  docs (editable docs people share and comment on; the default for any document, named as a doc or not: a document, report, proposal, resume, cover letter, letter, contract, policy, form, template, worksheet, essay, handbook, guide, how-to, cheat sheet, SOP or other writing to keep, share, collaborate

• import-memory

  Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

• learn

  Use this skill when the user wants intellectual understanding — learning how or why something works, not getting a task done or soliciting Claude's judgment. Trigger for: - Explicit learning requests: teach, explain, ELI5, walk me through, quiz me, flashcards, "I'm rusty on"; definitions ("what is X

• morning

  Render the user's morning brief as a styled HTML artifact, or set it up as a recurring weekday task. Use only when the user explicitly asks to run, see, or set up their morning brief, or if they invoke /morning by name. A question about their day, schedule, or calendar is not by itself a request for

• test-driven-development

  Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Follow the red-green-refactor cycle: write a failing test first, then the minimal code to make it pass. Use when you need to prove that code works, when a bug report arrives, or when you're abou

• using-agent-skills

  Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

Subagents (4)

• code-reviewer

  Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.

• security-auditor

  Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.

• test-engineer

  QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.

• web-performance-auditor

  Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.

Hooks (1)

• SessionStart

  SCRIPT="${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"; [ -f "$SCRIPT" ] || SCRIPT="${CLAUDE_PROJECT_DIR}/.claude/hooks/session-start.sh"; [ -f "$SCRIPT" ]&& bash "$SCRIPT" || true

Similar plugins