all publishers

whamp

@whamp source repo

66 published skills

  1. ▌
    Codegraph 5 · whamp bundle
    CodeGraph scout before broad grep/read. Use for repo explanation, navigation, diagnosis, runtime/reconnect flow, contract/RPC/schema tracing, refactor/cycle seams, dead-code cleanup, test targeting, and code review.
    3 repo stars
  2. ▌
    No Mistakes 2 · whamp
    Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach upstream. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.
    3 repo stars
  3. ▌
    Docs To Types 2 · whamp bundle
    Converts grill-with-docs output — CONTEXT.md glossaries, ADRs, and approved domain decisions — into typed architecture. Use after grill-with-docs when the user wants domain types, seams, adapters, errors, call stacks, and dependency rules expressed in code before business behavior.
    3 repo stars
  4. ▌
    Codegraph 4 · whamp
    Local symbol-and-relationship map of the repo. Use to see who calls what (blast radius) before editing a function, class, or method. The binary is at /arm/bin/cg.
    3 repo stars
  5. ▌
    Fuzzing 3 · whamp bundle
    Coverage-guided fuzzing for implementation and test work on input-processing and memory-safety boundaries. Use when a feature or bug touches parsers, lexers, decoders, deserializers, codecs, file formats, protocol handlers, malformed, chunked, or adversarial input, unsafe or FFI code, or crash, hang, and resource-exhaustion risks; also use when designing or running fuzz targets, engines, oracles, seeds and corpora, coverage campaigns, crash minimization, and regression conversion.
    3 repo stars
  6. ▌
    Testing 5 · whamp bundle
    Testing strategy and explicit behavioral evidence. Use for selecting test seams and levels, writing regression, unit, integration, contract, or browser tests, proving fixes, reviewing tests, diagnosing flakes, and interpreting coverage or mutation results. Use it to choose explicit examples, property-based testing, or fuzzing as the primary search mechanism for each risk.
    3 repo stars
  7. ▌
    Fuzzing 4 · whamp bundle
    Fuzzing for coverage-guided input search, target and campaign design, failure minimization, and regression replay. Use to assess or execute fuzzing at input-processing, protocol, file-format, unsafe-code, FFI, or memory-safety boundaries; also use for existing fuzz targets, campaigns, corpora, and discovered failures.
    3 repo stars
  8. ▌
    Property Based Testing 3 · whamp bundle
    Property-based testing for implementation and test work with broad structured behavior. Use when a feature or bug spans input combinations, round trips, encoding and decoding, serialization, normalization or idempotence, ordering or pagination, schema variants, stateful operation sequences, distributed or concurrent schedules, parsers or codecs with semantic invariants, or differential models; also use when designing or reviewing generators, shrinkers, properties, and counterexample handling.
    3 repo stars
  9. ▌
    Property Based Testing 4 · whamp bundle
    Property-based testing for quantified generated search, property review, and counterexample triage. Use when a broad domain, invariant, round trip, normalization rule, ordering relation, operation sequence, or schedule can challenge a compact independent oracle more effectively than a small explicit table; also use to design or review generators, shrinkers, properties, replay, and failure handling.
    3 repo stars
  10. ▌
    Ponytail 2 · whamp
    Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.
    3 repo stars
  11. ▌
    Ponytail Help 2 · whamp
    Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
    3 repo stars
  12. ▌
    Docs To Types · whamp bundle
    Converts grill-with-docs output — CONTEXT.md glossaries, ADRs, and approved domain decisions — into typed architecture. Use after grill-with-docs when the user wants domain types, seams, adapters, errors, call stacks, and dependency rules expressed in code before business behavior.
    3 repo stars
  13. ▌
    No Mistakes · whamp
    Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they reach upstream. Use when the user asks to run no-mistakes, gate or ship or validate their changes, push safely, asks you to do a task and then validate it, or invokes /no-mistakes.
    3 repo stars
  14. ▌
    Ponytail Help · whamp
    Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
    3 repo stars
  15. ▌
    Testing 2 · whamp bundle
    Testing design and maintenance for selecting test seams and levels, writing explicit regression, unit, integration, contract, or browser tests, proving bug fixes, reviewing tests, diagnosing flakes, and interpreting coverage or mutation results. Use `property-based-testing` directly for broad generated domains, invariants, operation sequences, or schedules; use `fuzzing` directly for coverage-guided exploration of parsers, protocols, unsafe code, or untrusted input.
    3 repo stars
  16. ▌
    Testing 3 · whamp bundle
    Testing strategy and explicit behavioral evidence. Use for selecting test seams and levels, writing regression, unit, integration, contract, or browser tests, proving fixes, reviewing tests, diagnosing flakes, and interpreting coverage or mutation results. Use it to choose explicit examples, property-based testing, or fuzzing as the primary search mechanism for each risk.
    3 repo stars
  17. ▌
    Fuzzing 2 · whamp bundle
    Coverage-guided fuzzing for implementation and test work on input-processing and memory-safety boundaries. Use when a feature or bug touches parsers, lexers, decoders, deserializers, codecs, file formats, protocol handlers, malformed, chunked, or adversarial input, unsafe or FFI code, or crash, hang, and resource-exhaustion risks; also use when designing or running fuzz targets, engines, oracles, seeds and corpora, coverage campaigns, crash minimization, and regression conversion.
    3 repo stars
  18. ▌
    Testing 4 · whamp bundle
    Testing strategy and explicit behavioral evidence. Use for selecting test seams and levels, writing regression, unit, integration, contract, or browser tests, proving fixes, reviewing tests, diagnosing flakes, and interpreting coverage or mutation results. Use it to map plausible failures to explicit examples, property-based testing, or fuzzing after inspecting the relevant code and tests.
    3 repo stars
  19. ▌
    Codegraph 2 · whamp bundle
    CodeGraph scout before broad grep/read. Use for repo explanation, navigation, diagnosis, runtime/reconnect flow, contract/RPC/schema tracing, refactor/cycle seams, dead-code cleanup, test targeting, and code review.
    3 repo stars
  20. ▌
    Property Based Testing 2 · whamp bundle
    Property-based testing for implementation and test work with broad structured behavior. Use when a feature or bug spans input combinations, round trips, encoding and decoding, serialization, normalization or idempotence, ordering or pagination, schema variants, stateful operation sequences, distributed or concurrent schedules, parsers or codecs with semantic invariants, or differential models; also use when designing or reviewing generators, shrinkers, properties, and counterexample handling.
    3 repo stars
  21. ▌
    Codegraph 3 · whamp bundle
    CodeGraph scout before broad grep/read. Use for repo explanation, navigation, diagnosis, runtime/reconnect flow, contract/RPC/schema tracing, refactor/cycle seams, dead-code cleanup, test targeting, and code review.
    3 repo stars
  22. ▌
    Brain · whamp bundle
    Use when working on a project with Brain agent memory management. Triggers on memory_commit, memory_branch tool usage, or when the project has a .memory/ directory.
    3 repo stars
  23. ▌
    Conductor · whamp bundle
    Context-driven development with spec-driven workflows, TDD-based task execution, track management, and phase checkpointing
    3 repo stars
  24. ▌
    Summary Judge · whamp bundle
    Compare and judge file summaries from pi-read-map vs standard read tool. Use when evaluating summary quality on large files (>2k lines). Trigger with "/skill:summary-judge <file-path>" to run full automated comparison and update demo/README.md.
    3 repo stars
  25. ▌
    Rlm · whamp bundle
    Process files too large to fit in context (>100KB, >2000 lines). Uses Python REPL for structural analysis, LLM queries for semantic reasoning, and subagents for final synthesis. Triggers - large file, big document, massive log, full codebase, entire repo, long transcript, context window exceeded.
    3 repo stars
  26. ▌
    Axi · whamp
    Agent eXperience Interface (AXI) — ergonomic standards for building CLI tools that agents use via shell execution. Use when building, modifying, or reviewing any agent-facing CLI.
    3 repo stars
  27. ▌
    Playwright CLI Axi · whamp
    Use playwright-cli-axi when controlling Playwright from an agent shell and when video recording, TOON output, or AXI-friendly browser automation matters.
    3 repo stars
  28. ▌
    Browser Tools · whamp bundle
    Lightweight Chrome automation toolkit with shared configuration, JSON-first output, and six focused scripts for starting, navigating, inspecting, capturing, evaluating, and cleaning up browser sessions.
    3 repo stars
  29. ▌
    Gemini CLI Integration · whamp bundle
    Use the gemini-cli-integration skill PROACTIVELY when analyzing large codebases, multiple files, or directories. Leverages Google Gemini's massive context window with @ syntax for file inclusion to handle comprehensive codebase analysis, implementation verification, and architectural understanding.
    3 repo stars
  30. ▌
    Kv Store Skill · whamp bundle
    A skill for interacting with a simple key-value store. Use this skill to get, set, and delete values from the store.
    3 repo stars
  31. ▌
    Strategy Synthesis · whamp
    Strategy Synthesis Skill
    3 repo stars
  32. ▌
    Advanced Web Search · whamp
    Advanced Web Search Skill
    3 repo stars
  33. ▌
    Strategy Generation · whamp
    Strategy Generation Skill
    3 repo stars
  34. ▌
    Execution Optimization · whamp
    Execution Optimization Skill
    3 repo stars
  35. ▌
    Environment Observation · whamp
    Environment Observation Skill
    3 repo stars
  36. ▌
    Predictive Intelligence · whamp
    Predictive Intelligence Skill
    3 repo stars
  37. ▌
    Runboard · whamp bundle
    Open a Herdr tail tab for a harness run when the user explicitly asks for a runboard, tail, Herdr tab, or raw log view. For new harness/run_batch.py monitoring, prefer the structured dashboard at scripts/run_dashboard.py reading results/_runs/<run_id>; this skill is the compatibility/tail workflow.
    3 repo stars
  38. ▌
    X Thread Fetch · whamp bundle
    Fetch a full X/Twitter thread — all posts with untruncated text plus images — without auth or the paid API. Use when the user wants to retrieve, extract, scrape, pull, save, or download an X/Twitter thread, tweet text, or tweet images, mentions a status URL or tweet id, or asks to get the content of a thread/post.
    3 repo stars
  39. ▌
    Benchmark Launch · whamp
    Use before preparing or executing a confirmed deep-swe-bench launch, especially when configs use advisor, observational-memory workers, subagents, local-vLLM shims, or any model beyond the main executor; use before claiming a launch is working.
    3 repo stars
  40. ▌
    Write Benchmark Thread · whamp
    Write a viral-but-honest X/Twitter thread for a benchmark or eval result (e.g. DeepSWE, ProgramBench, ponytail, pi-observational-memory runs). Use when the user asks to write, draft, rewrite, iterate on, or render a tweet thread about benchmark results, eval findings, A/B comparisons, agent evaluations, or model measurements, or says "thread", "tweet", "X post", or references the tweet-craft process. Enforces accuracy, human voice, and the accumulated review lessons. Read FEEDBACK_LOG.md before drafting.
    3 repo stars
  41. ▌
    Benchmark Social Graphics · whamp bundle
    Benchmark graphics. Use when creating social cards, README benchmark tables, chart images, X/Twitter graphics, or visual summaries from eval result artifacts where exact numbers, axes, labels, or datapoint placement matter.
    3 repo stars
  42. ▌
    Prompt Embedding Analysis · whamp
    Prompt embedding analysis. Use when clustering benchmark prompt/config text, comparing semantic neighbors, or separating prompt-shaped effects from behavioral wrappers in deep-swe-bench results.
    3 repo stars
  43. ▌
    Paired Trajectory Analysis · whamp bundle
    Paired trajectory analysis for benchmark churn. Use when comparing two configs on matched task/rep cells, explaining solve flips, diagnosing a local model against a frontier reference, separating net score from churn, or preparing evidence to improve a skill, prompt, tool, or harness surface from trajectory differences.
    3 repo stars
  44. ▌
    Benchmark Config Validation · whamp
    Use before adding or changing a deep-swe-bench config release, model leaf, provider/model API path, config lock, role declaration, usage parser, smoke contract, or extension/subagent worker usage accounting.
    3 repo stars
  45. ▌
    Codegraph · whamp bundle
    Local symbol-and-relationship map of the repo. Use to see who calls what (blast radius) before editing a function, class, or method. The binary is at /arm/bin/cg.
    3 repo stars
  46. ▌
    Fuzzing · whamp bundle
    Coverage-guided fuzzing. Use when selecting or writing fuzz targets for parsers, decoders, protocol handlers, unsafe or FFI code, or untrusted inputs; running cargo-fuzz, libFuzzer, AFL++, or Go fuzzing; designing fuzz oracles and corpora; analyzing coverage plateaus; or reproducing, minimizing, deduplicating, and converting crashes into regressions.
    3 repo stars
  47. ▌
    Testing · whamp bundle
    Testing design and maintenance. Use when choosing a test seam or level; writing or reviewing regression, unit, integration, contract, browser, JavaScript/TypeScript, or Rust tests; proving a bug fix; auditing AI-generated tests or suspected test slop; diagnosing flaky tests; interpreting coverage or mutation results; or deciding whether tests should be improved, quarantined, or removed. Routes property testing and fuzzing.
    3 repo stars
  48. ▌
    Ponytail · whamp
    Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", and whenever they complain about over-engineering, bloat, boilerplate, or unnecessary dependencies.
    3 repo stars
  49. ▌
    Property Based Testing · whamp bundle
    Property-based testing. Use for tests and reviews involving broad structured domains, parsers and codecs, canonicalizers and validators, compact postcondition oracles, differential models, stateful APIs and protocols, or concurrent schedules.
    3 repo stars
  50. ▌
    Bro · whamp bundle
    Restate the previous response in plain, concise language for a cold reader.
    3 repo stars
  51. ▌
    Herdr · whamp bundle
    Use Herdr sidecars for persistent or continuously observable work when `HERDR_ENV=1`. Also use when asked to control panes, layout, workspaces, or coding agents through Herdr.
    3 repo stars
  52. ▌
    Sideshow · whamp bundle
    Publish work to a hosted visual review and feedback loop.
    3 repo stars
  53. ▌
    Repo Cleanup · whamp bundle
    Audit and safely remove obsolete Git worktrees, repository-owned temporary artifacts, and inactive development databases.
    3 repo stars
  54. ▌
    Model Routing · whamp bundle
    Route delegated model portfolios across independent provider and subscription pools. Use when selecting models for delegated roles, planning multi-family review and synthesis, handling quota pressure, watching long-running work, or adding family diversity to implementation, debugging, visual work, and adversarial review.
    3 repo stars
  55. ▌
    Worktree First · whamp bundle
    Worktree-first isolation routes substantive implementation through Lane in adopted repositories and a plain Git worktree elsewhere. Use before a feature, nontrivial fix, substantial refactor, delegated implementation, or deliberate Lane adoption.
    3 repo stars
  56. ▌
    Clear Writing · whamp bundle
    Write or revise durable human-facing prose with plain force. Use for docs, READMEs, API guides, runbooks, commit messages, PR descriptions, reports, error messages, UI copy, or explicit requests for clearer, shorter, sharper, more direct, or less AI-sounding prose.
    3 repo stars
  57. ▌
    Explain Diff HTML · whamp bundle
    Build an interactive HTML explainer of a code change (a diff, branch, or PR). Use when the user wants a rich walkthrough of what changed and why.
    3 repo stars
  58. ▌
    First Principles · whamp bundle
    Interactive first-principles reasoning that separates facts, constraints, assumptions, analogies, and unknowns before rebuilding options from fundamentals.
    3 repo stars
  59. ▌
    Distilling Skills · whamp
    Use when the user wants to find, evaluate, and combine agent skills on a topic into a single best-of-breed version. Triggers on requests to search skills.sh, improve an existing skill by finding alternatives, or build a concentrated skill from multiple sources.
    3 repo stars
  60. ▌
    Ban Type Assertions · whamp bundle
    Ban `as` type assertions via the native oxlint `typescript/consistent-type-assertions` rule (`assertionStyle: 'never'`), replacing them with compiler-verified type-safe alternatives. Use when enabling the assertion ban in a project or fixing violations in an existing one.
    3 repo stars
  61. ▌
    Nvidia Cuda Performance · whamp bundle
    NVIDIA CUDA performance engineering. Use when estimating, diagnosing, designing, reviewing, implementing, or validating GPU performance for CUDA kernels, CUDA-backed applications, RTX 3090 or SM86 targets, LLM inference, or intra-host multi-GPU scaling.
    3 repo stars
  62. ▌
    Omarchy Free Disk Space · whamp bundle
    Safely audit and reclaim disk space on Omarchy and Arch Linux systems. Use when asked to free up disk space, clean an Omarchy computer, find what is using storage, audit disk usage, clean Arch package caches, or check Snapper disk usage.
    3 repo stars
  63. ▌
    Pastlight Agents Pointer · whamp bundle
    Add the concise Pastlight pointer to a project's AGENTS.md.
    3 repo stars
  64. ▌
    Dynamic Workflow Patterns · whamp
    Use when the user asks for a workflow, dynamic workflow, fan-out, multi-agent orchestration, ultracode-style work, large-scale verification, adversarial review, tournament selection, or decomposable research/refactor tasks. Teaches when to use Pi's workflow tool and which orchestration pattern to choose.
    3 repo stars
  65. ▌
    Perform Like Jeff And Sanjay · whamp bundle
    Performance engineering for a single binary. Use when designing or reviewing performance-sensitive code, estimating resource costs, diagnosing a measured bottleneck or flat profile, implementing a performance change, or validating a claimed speedup.
    3 repo stars
  66. ▌
    Integrate Napkin Agent Skills · whamp bundle
    Integrate a Napkin vault with the files created by setup-matt-pocock-skills.
    3 repo stars