finding-unknowns-skills

In the author's own words, from each skill's SKILL.md.

• agent-interface-design

  Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.

  skills/agent-interface-design/SKILL.md on GitHub (opens in a new tab)

• assumption-test

  Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.

  skills/assumption-test/SKILL.md on GitHub (opens in a new tab)

• blindspot-pass

  Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."

  skills/blindspot-pass/SKILL.md on GitHub (opens in a new tab)

• brainstorm-prototypes

  Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.

  skills/brainstorm-prototypes/SKILL.md on GitHub (opens in a new tab)

• change-quiz

  After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.

  skills/change-quiz/SKILL.md on GitHub (opens in a new tab)

• context-audit

  Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.

  skills/context-audit/SKILL.md on GitHub (opens in a new tab)

• implementation-notes

  Keep a running implementation-notes.md during a build, logging every deviation from the plan and every discovered edge case. Use whenever implementing against an agreed plan or spec, especially in long autonomous sessions.

  skills/implementation-notes/SKILL.md on GitHub (opens in a new tab)

• implementation-plan

  Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.

  skills/implementation-plan/SKILL.md on GitHub (opens in a new tab)

• interview-me

  Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.

  skills/interview-me/SKILL.md on GitHub (opens in a new tab)

• pitch-packager

  Package a finished piece of work (spec, prototype, implementation notes) into a single document that gets reviewers to understanding and approval fast. Use when the user needs buy-in, a review, or a shareable summary of what was built and why.

  skills/pitch-packager/SKILL.md on GitHub (opens in a new tab)

• progressive-disclosure

  Split an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.

  skills/progressive-disclosure/SKILL.md on GitHub (opens in a new tab)

• reference-hunt

  Use existing source code as the specification when the user can't describe what they want in words. Use when the user points at a library, module, folder, or site and says "like this," even if it's in a different language or stack.

  skills/reference-hunt/SKILL.md on GitHub (opens in a new tab)

• regression-proof

  Fix a reported bug with a regression test that demonstrably fails on the original behavior and passes after the fix. Use when implementing a bug fix or checking whether a proposed fix actually addresses a reported failure. Not a general coverage audit or new-feature workflow.

  skills/regression-proof/SKILL.md on GitHub (opens in a new tab)

• test-blindspots

  Find consequential behavior that a passing test suite does not establish, using focused exploratory checks. Use when the user asks what green tests miss or wants confidence in test coverage for a specific change. Not a general code review, routine test run, or debugging workflow for an already failing test.

  skills/test-blindspots/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• Wazaby tw93 🥷 Engineering habits you already know, turned into skills AI assistants like Claude Code, Codex and Cursor can run. 7.3k stars · 8 skills
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 97.3k stars · 13 skills
• khazix-skillsby KKKKhazix 数字生命卡兹克开源的 AI Skills 合集 | Agent Skills: leader（帮你定义目标）, neat-freak 洁癖, hv-analysis, khazix-writer & more — Claude Code, Codex & 40+ agents 21.4k stars · 6 skills
• geo-sleuthby Oldcircle An agent skill that finds where a photo was taken — OpenStreetMap geometry, elevation skylines, satellite imagery and street view — and sho… 3k stars · 1 skill
• agent-skills-platformby FrancyJGLisboa Build tested agent skills and govern their lifecycle through a user-defined marketplace: evidence, discovery, updates, rollback, quarantine… 2.4k stars · 6 skills
• Pretty-mermaid-skillsby imxv AI Agent Skill to generate and render beautiful Mermaid diagrams as SVG or terminal ASCII — 15 themes, 6 diagram types, batch CLI, no brows… 1.5k stars · 1 skill