Explore skills
Showing 27691–27720 of 77079 skills
Write and improve test-owned code: tests, test scripts, fixtures, evals, and test-only helpers. Use whenever Codex is asked to create or change test code. Its only job is to produce the strongest practical tests in the repository's existing harness, run them, and fix defects in the test code.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexRoute production coding tasks to the user-level Shell, TypeScript, Python, or Rust Codex workflow. Use for "codex-coder", "Codex write", "generate with Codex", language migrations, or mixed Shell/TypeScript/Python/Rust implementation when Codex should choose the correct language specialist automatically.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexImplement and refactor production Python, FastAPI, Pydantic, async, and migrations.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexImplement and refactor production shell scripts, command-line tools, automation, process wrappers, and Git or infrastructure helpers with reliable failures, useful logs, and machine-readable output.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexImplement and refactor production TypeScript/TSX, strict types, APIs, and migrations.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexUse Reach Instant Messenger for a response now and Agent Email for saved messages or tasks handled later. Contact agents, inspect replies, or manage reachable conversations. Full task ownership transfer belongs to handoff.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexWrite, revise or review a charter: the one document that tells an executor what to deliver, what is out of bounds, what the owner already decided, and how each success check will be proven. Use when work needs a written brief before someone else does it, or when asked to write, change or check a charter.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexCarry out a released charter to a proven result: plan only as much as the work needs, do the work through the project's own workers, prove every success check with a recorded real run, get one independent review, and close honestly. Invoke explicitly as `$deliver <charter>` (Codex) or `/deliver <charter>` (Claude, Cursor), or the way your agent invokes a skill, or when a dispatch names you the executor of a charter.
sno-ai/sno-station-skills
Stars: 865Claude CodeCodexEaster-egg alias for /catchup. Same return-from-absence briefing, squeezier name. Use exactly like /catchup — all flags pass through unchanged.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexCompatibility alias for the Elixir/Phoenix plugin's Ecto constraint debugger. Invoke explicitly with /ecto:constraint-debug.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexCompatibility alias for the Elixir/Phoenix plugin's N+1 query checker. Invoke explicitly with /ecto:n1-check.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexCompatibility alias for the Elixir/Phoenix plugin's LiveView assigns audit. Invoke explicitly with /lv:assigns.
oliver-kriska/claude-elixir-phoenix
Stars: 576Claude CodeCodexGuide for editing videos where the primary content is people talking — talking-head / 口播, interview / 访谈, lecture, tutorial, podcast, course content, and similar talking-driven formats. Use when the user wants speech editing on a talking video (剪口播 / 口播剪辑 / 去口癖 / clean up fillers / smooth speech), motion graphics layered onto talking video (口播加 MG / 加动画), or B-roll on a talking video (加 B-roll / add B-roll). For motion graphics specifically, use this together with the active Motion Graphics skill/workflow available in the current OpenChatCut environment — this skill adds talking-specific guidance (speech-rhythm timing, frame-aware placement, subject/caption protection, placement verification).
0xsline/OpenChatCut
Stars: 3.1kClaude CodeCodexSession-start briefing: where did I leave off, what is in flight, what needs attention. One tested script reads git, the journal (followups, running work, cadences) and tracked projects and prints every fixed-threshold check that fires; JellyRock's own aggregator adds open PRs, high-engagement bugs, recent bug reports, current-branch CI, pending handoffs, open upstream-watch issues (Jellyfin releases and release candidates, Roku OS), recent ADRs, tech debt and architecture-doc staleness. Ends with one Suggested next move that hands off to /log, /done, /issue-triage, /runtime-triage, /ci-triage or /server-upgrade. Mandated by AGENTS.md's catchup-discipline rule: run at the start of any genuine new session, after a multi-day gap, or whenever you ask what the state of the world is.
jellyrock/jellyrock
Stars: 52Claude CodeCodexMark journal work complete: close an existing followup by its fid, or ship the in-flight `running` cursor. Companion to /log, which captures new entries; /done closes existing ones. Finds the entry, proves the work actually landed, then closes it: a followup through the journal script (the entry is removed; git is the history; on main it also gains a Recently shipped line), the cursor by a direct edit. Nothing is committed on its own: the closure rides in the commit of the change that prompted it. No confirm gate on a proven closure. Pure local-file edits, apart from read-only checks that the work landed. Use when the work an entry describes is committed on this branch (pushed or merged is not required, since the closure rides in the same change set) and its journal entry needs closing. Not for capturing new entries (use /log), and not for work that is still uncommitted, undeployed or partial (don't pre-mark optimistically).
jellyrock/jellyrock
Stars: 52Claude CodeCodexThis skill should be used ONLY when the user explicitly types "/resume-project" (optionally with a slug). It loads an existing tracked project in the projects folder (docs/projects/ by default) and the surrounding context so work can continue cleanly, using the project's Next-session kickoff as the starting prompt. Do NOT auto-invoke when the user merely opens the repo or mentions past work.
jellyrock/jellyrock
Stars: 52Claude CodeCodexGet a second opinion from a reviewer with a clean context. Runs only when the user types /second-opinion (with what to review), or replies second-opinion on a decision screen; never on its own. One item comes back improved (ranked problems with evidence, fixes, what is missing); several come back compared without bias (neutral shuffled labels, criteria written before the options are seen, a winner and what would flip it, an option nobody listed). The report is shown word for word, then a point-by-point response, then the screen again with changes marked. NOT for bugs in a code diff (use /code-review) or for how a skill ran (a skill audit).
jellyrock/jellyrock
Stars: 52Claude CodeCodexAnalyze and document a project's backend patterns — API design, data access, service structure. Use when the user wants a backend-only architecture analysis.
ayoubben18/ab-method
Stars: 193Claude CodeCodexAnalyze and document a project's frontend patterns — component structure, state management, conventions. Use when the user wants a frontend-only architecture analysis.
ayoubben18/ab-method
Stars: 193Claude CodeCodexAnalyze a project's architecture end to end — extract domain language, map the tech stack, document frontend and backend patterns. Use when onboarding a new codebase or refreshing the architecture baseline.
ayoubben18/ab-method
Stars: 193Claude CodeCodexProduce a ready-to-run prompt for an autonomous /goal loop. Use when the user wants to hand off one continuous objective with a verifiable stop condition to run autonomously.
ayoubben18/ab-method
Stars: 193Claude CodeCodexCreate a holistic task — deepen the code it touches, design new seams, and break it into composed missions. Use when the user wants to start a new feature, fix a bug, or begin implementation work.
ayoubben18/ab-method
Stars: 193Claude CodeCodexExtend an existing goal — broaden or add to its objective, building on top of what the earlier /goal run already implemented. Use when the user wants to expand a goal after a /goal run.
ayoubben18/ab-method
Stars: 193Claude CodeCodexAppend new missions to an existing task. Use when requirements changed or scope grew on a task already underway.
ayoubben18/ab-method
Stars: 193Claude CodeCodexContinue an existing task from its progress tracker. Use when the user wants to resume, continue, or pick up earlier task work.
ayoubben18/ab-method
Stars: 193Claude CodeCodexRefresh architecture and domain documentation after impactful changes. Use when code has drifted from the documented architecture.
ayoubben18/ab-method
Stars: 193Claude CodeCodexSearches current documentation, release notes, API references and public repository issues for libraries, frameworks, SDKs, APIs and CLI tools with `firecrawl developer`. Use before answering when the user names a version, is upgrading, pastes an error from a library or tool, or asks how to use, configure or migrate a specific library or API. Model knowledge stops at a training cutoff and misses new releases, renamed APIs, changed defaults and recent fixes, so when a version, option, error or API is unfamiliar or may have changed, look it up instead of guessing. Also checks whether a bug was fixed and in which release. Not for general programming concepts, code that uses no specific library, or refactoring code the user supplied.
firecrawl/skills
Stars: 160Claude CodeCodexFind the papers that answer a research query in Firecrawl's research paper index — a corpus of paper abstracts whose largest share is biomedical and life-science literature (PubMed, bioRxiv, medRxiv), alongside arXiv preprints in CS, physics, and math — using semantic search, semantic and structural expansion, and in-body verification. Use this skill for literature-finding and paper-retrieval tasks of any kind, including clinical, biomedical, drug, gene, disease, and other life-science questions, whether the answer is a single paper or a full multi-paper set. The index is reached only through the `firecrawl_research_*` MCP tools or the `firecrawl research` CLI subcommands. Calling `firecrawl_search` with its `categories` option set to `["research"]` is a different feature — it filters ordinary web search to research-affiliated websites (the list includes PubMed, bioRxiv, medRxiv, arXiv, and publisher sites) and returns page results from them, without querying the paper records in this index.
firecrawl/skills
Stars: 160Claude CodeCodexFind the published business contacts of companies with Firecrawl, whether the user names them or describes them by type and place: press and media, sales, partnerships and support inboxes, shared business phone numbers and official contact forms, taken from the companies' own websites. Use when the user asks how to contact a company or wants published business emails, phone numbers or press, sales, support or partnership contacts, since contact pages change and an address must come from the page, not memory. Not for named people's details (use firecrawl-lead-research) or finding people to reach out to (use firecrawl-lead-gen).
firecrawl/skills
Stars: 160Claude CodeCodexHelp fantasy players make start/sit, waiver, streaming, trade, draft and keeper decisions using current player news, usage, matchups and their league's scoring. Use for choosing between players, finding pickups, evaluating a deal or filling a roster need, even without an explicit research request. Excludes generic sports scores, betting and changing league rosters.
firecrawl/skills
Stars: 160Claude CodeCodex