Skip to content

Instruction-only agent skills

2,929 instruction-only agent skills, out of 3,419 agent skills listed. Popular ones include Rea analysis optimization, Rea changelog update and Rea ci tests audit. These skills contain instructions and reference files but no scripts, so they run no code of their own. Each one lists the tools it asks for and how to install it in Claude Code, Codex, Cursor and other agents.

Showing 2,851–2,880 of 2,917

  1. Detect, activate, or deactivate bundled knowledge patches.

    • Open source
    • 25 GitHub stars
  2. Report bundled patch versions, activation state, age, and missing artifacts.

    • Open source
    • 25 GitHub stars
  3. Route technology work to matching bundled knowledge patches.

    • Open source
    • 25 GitHub stars
  4. Two-layer AI-tell audit of any text — deterministic scanner (lexicon, constructions, stylometry with line numbers) plus a blind semantic jud

    • Open source
    • 25 GitHub stars
  5. One brief, N posts, N genuinely different people — voice-isolated writers, cross-post overlap detection, per-post verification receipts

    • Open source
    • 25 GitHub stars
    • Marketing and SEO
  6. Rewrite existing text so it reads human — either scrubbed-and-souled in its own register, or fully re-voiced as one of the roster's people

    • Open source
    • 25 GitHub stars
  7. Front door and router for the idiolect voice engine

    • Open source
    • 25 GitHub stars
  8. Build and maintain the user's OWN voice profile from continuously captured writing plus explicit samples — status, build/refresh, add sample

    • Open source
    • 25 GitHub stars
  9. Create a new voice profile — from a writing corpus (measured, not vibed), or invented to fill a gap in the roster

    • Open source
    • 25 GitHub stars
  10. Write a social post in one of the roster's voices (or the user's own `self` voice) — platform-native, craft-floored, scanner-verified

    • Open source
    • 25 GitHub stars
  11. Creates and manages isolated cloud sandboxes (secure code execution environments with dedicated runtimes) on the Daytona platform, through t

    • Open source
    • 23 GitHub stars
  12. Run builds, tests, and other tooling inside a reproducible, containerized dev environment via the `ilo` CLI instead of on the host

    • Open source
    • 21 GitHub stars
  13. LOG-UFPB's internal quick reference (group conventions, recommended tools, solvers and caveats from the group's own experience)

    • Open source
    • 21 GitHub stars
  14. Use when items need categorical triage (critical/warning/ok), not numeric scoring

    • Open source
    • 14 GitHub stars
  15. Use when you want to stress-test a proposal, plan, or findings before acting on them

    • Open source
    • 14 GitHub stars
  16. Use when a goal is too large to tackle as one unit

    • Open source
    • 14 GitHub stars
  17. Use when deciding between two approaches and you need a structured tradeoff comparison

    • Open source
    • 14 GitHub stars
  18. Use when you want to browse available skills or find the right pipeline for a workflow

    • Open source
    • 14 GitHub stars
  19. Use when prior output is too verbose and needs condensing

    • Open source
    • 14 GitHub stars
  20. Use when you have a goal but don't know which skill fits

    • Open source
    • 14 GitHub stars
  21. Use when prior findings are too sparse for action

    • Open source
    • 14 GitHub stars
  22. Use when you need to remove irrelevant items from a collection

    • Open source
    • 14 GitHub stars
  23. Use when you need to research a topic before analyzing it

    • Open source
    • 14 GitHub stars
  24. Use when multiple agents or skills produced separate findings that need combining into one list

    • Open source
    • 14 GitHub stars
  25. Use when you have items to execute and need to know the right order

    • Open source
    • 14 GitHub stars
  26. Use when you have items and need to know which matter most

    • Open source
    • 14 GitHub stars
  27. Use when you've decided on an approach and need to see the structure before implementing

    • Open source
    • 14 GitHub stars
  28. Use when items need reformatting without changing the collection (e.g., as ticket titles, test cases, or for a different audience)

    • Open source
    • 14 GitHub stars
  29. Use when prior findings contain claims that need fact-checking against code, docs, or reality

    • Open source
    • 14 GitHub stars
  30. Use when you need to research, analyze, compare, plan, or structure thinking and aren't sure which primitive to reach for

    • Open source
    • 14 GitHub stars