Skip to content
AI Marketplaces Leaderboard

Skillquiver

ChatGPT plugin

Plan, code, debug, and review.

View in ChatGPT directory

Skillquiver is a collection of 23 reusable Agent Skills for planning, implementation, debugging, review, verification, UI, host boundaries, and safe environment maintenance. The public plugin works in ChatGPT and Codex; the same source catalog also supports Claude Code. It has no hosted backend, account, authentication, MCP server, bundled hooks, or app UI, and runs only through host-approved tools.

Featured
No

not on the featured shelf

Movement

From our daily snapshots over the last 30 days.

Rank by placement

#11254of 11,3608,922places down24h8,816places down7d
#1,440#4,117#6,794#9,471Oct 6Oct 12Oct 18Oct 24Oct 30Nov 4

Rank in Developer tools

#871of 900705places down24h695places down7d
#96#308#520#732Oct 6Oct 12Oct 18Oct 24Oct 30Nov 4

In its category

How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.

Developer tools871st of 900 by placement
#PluginPosition7d
869AgentMart Site Check#11184—
870Matt Skills Curated#112509,941places down
871SkillquiverThis page#112548,816places down
872Mermaid Diagrams#112568,828places down
873Skill Craft#112576,408places down

All 900 Developer tools plugins

Example prompts

  • “Turn this feature idea into a decision-complete implementation plan.”
  • “Diagnose this failing test systematically and verify the root cause.”
  • “Review this code change and report only evidence-backed findings.”

Skills

  • automate-ui

    Automates web and desktop UIs while capturing evidence that separates navigation from verified behavior. Use when a task requires site navigation, browser reproduction, or native app operation. For one existing framework-free HTML page, use design-ui instead.

  • brainstorming

    Explores user intent, requirements, and design before implementation. Use when starting a new feature, component, or behavior change whose requirements or design are not yet agreed; skip for trivial single-file changes the user has already specified.

  • communicate-clearly

    Controls report length while preserving evidence and explains external sources without overstating them. Use when a user requests concise handoffs, set verbosity, or plain-language explanations of dense material.

  • design-ui

    Builds accessible interfaces and verifies renders. Use when creating or redesigning a page, dashboard, or static HTML file.

  • diagnose-systematically

    Finds root causes through reproduction and falsifiable experiments. Use when a failure, flaky behavior, or regression lacks a demonstrated cause.

  • dispatching-parallel-agents

    Dispatches one subagent per independent problem. Use when two or more investigations or fixes can proceed concurrently without shared state or sequential dependencies.

  • engineer-prompts

    Builds or audits testable prompt contracts with explicit outcomes, permissions, tools, evidence, and stop conditions. Use when writing reusable agent prompts, system prompts, or prompts with unclear success criteria.

  • execute-durably

    Runs long or interruption-prone work from a durable state file with falsifiable criteria and evidence. Use when work spans turns, risks compaction, or must resume after interruption.

  • executing-plans

    Executes a written implementation plan inline, task by task, stopping only on blockers. Use when a plan exists and subagent dispatch is unavailable, or the user wants the plan executed in a separate session.

  • finishing-a-development-branch

    Guides integration of a finished branch: verify tests, present merge/PR/keep/discard options to the user, and clean up worktrees. Use when implementation is complete, all tests pass, and the work needs to be integrated.

  • handle-host-boundaries

    Handles unavailable named capabilities and destructive filesystem roots. Use when a required tool, command, picker, dialog, gate, or form may be unavailable; apply before acting even if the prompt asks to assume consent.

  • receiving-code-review

    Verifies code review feedback before implementation and pushes back with evidence when a claim is wrong. Use when feedback is unclear, risky, or technically questionable.

Show all 23
  • refactor-safely

    Refactors working or legacy code without changing observable behavior, using characterization tests when needed. Use when code is messy, nested, duplicated, or uncovered.

  • requesting-code-review

    Dispatches a bounded reviewer and preserves verified findings. Use when completed work needs read-only review before merge.

  • research-systematically

    Runs source-bound research and version-matched documentation lookup. Use when comparisons, experiments, benchmarks, investigations, or external library, SDK, CLI, and API facts must be verified.

  • skillquiver-doctor

    Audits the current ChatGPT, Claude Code, or Codex host for conflicting skills, plugins, and persistent hooks, then offers reversible per-item repairs. Use when skills duplicate, shadow, double-fire, load at the wrong time, or when the user asks to doctor or clean up Skillquiver conflicts.

  • solve-efficiently

    Routes multi-module work with progressive discovery, matched effort, and context economy. Use when boundaries are unclear, context must stay small, or a durable project map is needed.

  • subagent-driven-development

    Executes an implementation plan by dispatching one subagent per task with per-task review gates, keeping the orchestrator's context small. Use when executing plans with independent tasks in the current session.

  • test-driven-development

    Runs a recorded red-green-refactor cycle. Use when implementing a feature, bug fix, or behavior change.

  • using-git-worktrees

    Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

  • verification-before-completion

    Use when about to claim work is complete, fixed, or passing, before committing or creating PRs; requires running verification commands and confirming output before making any success claims. Do not load at task start or separately when design-ui's bounded static-page capture applies.

  • verify-work

    Independently audits finished work — verifies a delivery or completion claim against real evidence. Use when asked to double-check that something just finished actually works, confirm a completion claim, judge release readiness, or find unsupported claims.

  • writing-plans

    Creates implementation plans with interfaces, tests, and open decisions. Use when a multi-step change needs planning.

Categories
Made by
Saul Almonte · Website
Sign-in
On Install
Capabilities
Read project files and relevant local context., Write project files when the user's task authorizes changes., Run host-approved local development commands and tests., Use optional host-provided browser, UI automation, or subagent capabilities when available.
Availability
Available
Version
2.1.0
Keywords
agent-skills, chatgpt, claude-code, codex, developer-tools
Created
August 15, 2026
More info
Sponsorship
Promote this plugin