All authors
Claude Skills by Neeeophytee
github.com/Neeeophytee40 skills0 installs33 views
- Agent Interface DesignDesign 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.Votes: 0GitHub stars: 339
- Assumption TestTest 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.Votes: 0GitHub stars: 339
- Blindspot PassSurface 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."Votes: 0GitHub stars: 339
- Brainstorm PrototypesGenerate 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.Votes: 0GitHub stars: 339
- Change QuizAfter 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.Votes: 0GitHub stars: 339
- Context AuditAudit 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.Votes: 0GitHub stars: 339
- Implementation NotesKeep 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.Votes: 0GitHub stars: 339
- Implementation PlanWrite 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.Votes: 0GitHub stars: 339
- Interview MeInterview 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.Votes: 0GitHub stars: 339
- Pitch PackagerPackage 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.Votes: 0GitHub stars: 339
- Progressive DisclosureSplit an oversized skill, CLAUDE.md, or spec into an entry file plus files that load only when they're needed.Votes: 0GitHub stars: 339
- Reference HuntUse 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.Votes: 0GitHub stars: 339
- Regression ProofFix 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.Votes: 0GitHub stars: 339
- Test BlindspotsFind 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.Votes: 0GitHub stars: 339
- 18f ContentDraft, rewrite, or audit inclusive US digital-government content using an independently expressed interpretation of the 18F Content Guide. Use for public-service websites, forms, applications, transactional messages, help content, notices, and government digital experiences that should help people complete a task with minimal bureaucratic burden.Votes: 0GitHub stars: 57
- Apple Interface WritingDraft, rewrite, or audit concise interface text using an independently expressed reference-only interpretation of Apple's Human Interface Guidelines for writing. Use for buttons, labels, settings, alerts, errors, onboarding, notifications, permissions, empty states, and multi-screen app flows where wording must make actions and consequences clear in limited space.Votes: 0GitHub stars: 57
- Cdc Clear CommunicationDraft, rewrite, or audit evidence-based public-health communication using an independently expressed interpretation of the CDC Clear Communication Index. Use for patient explanations, health campaigns, risk and emergency messages, public-safety notices, and educational health material that must make one message and the audience's next action unmistakable.Votes: 0GitHub stars: 57
- Github DocsDraft, rewrite, or audit approachable developer product documentation using an independently expressed interpretation of the GitHub Docs style. Use for product workflows, how-to guides, conceptual overviews, troubleshooting, security guidance, and documentation that should move developers from prerequisites to a verified outcome.Votes: 0GitHub stars: 57
- Gitlab DocsDraft, rewrite, or audit concise product and engineering documentation using an independently expressed interpretation of the GitLab documentation style. Use for product guides, configuration, administration, tutorials, troubleshooting, contributor docs, and technical pages that must be searchable, precise, and localization-friendly.Votes: 0GitHub stars: 57
- Google Developer DocsDraft, rewrite, or audit developer documentation using an independently expressed interpretation of the Google developer documentation style. Use for API guides, tutorials, concepts, setup instructions, code explanations, command-line documentation, and technical content for a global developer audience.Votes: 0GitHub stars: 57
- GovukDraft, rewrite, or audit plain-language public-service content using an independently expressed interpretation of GOV.UK content design. Use for eligibility pages, government guidance, policy explanations, forms, transactions, public notices, and content that must help people make a decision or complete a service task.Votes: 0GitHub stars: 57
- Kubernetes DocsDraft, rewrite, or audit Kubernetes and cloud-native documentation using an independently expressed interpretation of Kubernetes documentation style. Use for concepts, tasks, tutorials, references, configuration, operations, and version-sensitive guidance involving clusters, workloads, APIs, kubectl, or Kubernetes resources.Votes: 0GitHub stars: 57
- Mailchimp ContentDraft, rewrite, or audit friendly customer and product communication using an independently expressed reference-only interpretation of Mailchimp's content guidance. Use for customer education, product copy, campaign guidance, onboarding, help messages, newsletters, and brand content that should be plainspoken, empathetic, and lightly playful only when the situation permits.Votes: 0GitHub stars: 57
- Mdn Web DocsDraft, rewrite, or audit web-platform documentation using an independently expressed interpretation of MDN Web Docs writing guidance. Use for HTML, CSS, JavaScript, Web API references, browser-facing concepts, tutorials, learning material, compatibility notes, and examples for web developers at a stated experience level.Votes: 0GitHub stars: 57
- Microsoft Writing StyleDraft, rewrite, or audit friendly, concise product and technical UX content using an independently expressed reference-only interpretation of Microsoft writing guidance. Use for product help, setup, support, interface text, error messages, and technical content that should feel conversational, scannable, global, and action-oriented.Votes: 0GitHub stars: 57
- Nasa Technical WritingDraft, restructure, or audit evidence-led scientific and engineering reports using an independently expressed reference-only interpretation of official NASA technical-publication guidance. Use for test and experiment reports, design descriptions, technical memoranda, engineering analyses, and scientific publications that must preserve measurements, conditions, limitations, and traceability from evidence to conclusions.Votes: 0GitHub stars: 57
- Nhs Health ContentDraft, rewrite, or audit patient-facing health and service content using an independently expressed reference-only interpretation of official NHS content guidance. Use for symptoms and conditions pages, appointment messages, treatment explanations, health-service instructions, and digital health journeys that must remain clinically accurate, inclusive, accessible, and explicit about next steps.Votes: 0GitHub stars: 57
- Red Hat DocsDraft, rewrite, or audit modular enterprise technical documentation using an independently expressed interpretation of the Red Hat supplementary style guide. Use for administration, installation, configuration, security, troubleshooting, procedures, concepts, and references that must be precise, reusable, and supportable across product versions.Votes: 0GitHub stars: 57
- Sec Plain EnglishDraft, rewrite, or audit investor-facing financial and legal disclosure using an independently expressed interpretation of official SEC plain-English guidance. Use for prospectus summaries, risk factors, shareholder letters, offering materials, and securities disclosures that must be easier to understand without losing any material fact, qualification, condition, or uncertainty.Votes: 0GitHub stars: 57
- W3c Technical ReportsDraft, restructure, or audit specification-style technical reports using an independently expressed reference-only interpretation of W3C editorial guidance. Use for protocols, standards, interoperability documents, conformance requirements, and technical specifications that must separate normative requirements from explanation and define precise, testable behavior without inventing requirements.Votes: 0GitHub stars: 57
- Advisor Call BudgetEnforce a hard cap and a drift-check when a cheap executor model consults an expensive advisor model, and compute the effective cost from actual call counts instead of a benchmark's assumed rate. Use when the user adopts the advisor or orchestrator pattern, pairs a cheap model with an expensive reviewer, or quotes a benchmark discount like "63% of the price".Votes: 0GitHub stars: 18
- Cheap Swap GuardBefore swapping any workload to a cheaper model, declare the cases the premium model still dominates and prove they keep routing to premium. Use when the user wants to "just switch" to a cheaper model (text, image, or video), or asks whether a cheap model is good enough to replace an expensive one.Votes: 0GitHub stars: 18
- Context DietCut agent token spend by shrinking what enters the context window. Index the repo or corpus once and query it instead of re-reading files on every question. Use when the user complains their coding agent burns tokens, the context fills up fast, the same files get read repeatedly, or the bill scales with conversation length.Votes: 0GitHub stars: 18
- Free Model TriageRoute high-volume, low-stakes triage (reading piles, inbox summaries, needs-reply flags) to a free model with a strict output schema. Use when the user wants one-line summaries of many items cheaply, asks to triage email, articles, or reports with AI, or wants to decide what's worth reading without paying premium rates for it.Votes: 0GitHub stars: 18
- Free Tier Batch PlanSize a big one-time batch job against a free tier's rate limit and token budget BEFORE starting it, with a proven wall-clock ETA. Use when the user wants to label a dataset, summarize an archive, or process a large backlog for free (or on a tiny rate limit), or asks "will this finish overnight?"Votes: 0GitHub stars: 18
- Model BakeoffChoose a model with evidence by running the few prompts that actually matter across candidate models inside a free tier's caps, picking by a stated criterion. Use when the user asks "which model should I use", wants to evaluate a newly launched model, or is choosing between models for a specific task.Votes: 0GitHub stars: 18
- Reasoning Effort ThrottleStop paying for deep reasoning on easy turns by setting a modest default reasoning effort and escalating per task. Use when the user runs a reasoning model in an agent and the bill is dominated by output or thinking tokens, or asks about reasoning_effort, thinking budgets, or why a cheap model is still expensive to run.Votes: 0GitHub stars: 18
- Route Cheap Escalate HardCut LLM spend by routing bulk work to a cheap model and escalating only the hard turns to a premium one. Use when the user says their AI bill is too high, asks to "use a cheaper model", or wants two-tier model routing without losing quality on the hard tasks.Votes: 0GitHub stars: 18
- Tested FallbackPin an open-weights fallback model with a tested-on date and real smoke prompts, so a pulled or deprecated model is a two-minute config swap instead of a lost week. Use when the user worries a model could vanish or be deprecated, builds anything important on one model, or asks about model failover and resilience.Votes: 0GitHub stars: 18
- Token Receipts AuditAttribute AI usage by tokens AND dollars so a high-volume cheap model is never mistaken for the expensive one. Use when the user asks where their AI spend actually goes, why the bill is high, which model is costing the most, or wants a usage audit across agents and models.Votes: 0GitHub stars: 18