Explore skills
Showing 30301–30330 of 77079 skills
Use when a task may benefit from a bounded subagent for implementation, large-codebase discovery at task start, independent review, requested or pre-commit code simplification, or expert work on complex decisions, modeling, automation, or repeated failures. The main agent chooses whether to delegate and accepts the result. Do not use for simple questions or short work with no meaningful review or delegation.
oil-oil/codex-team-mode
Stars: 237Claude CodeCodexDevelopment conventions and patterns for Agentrium (formerly claude-terminal). TypeScript Vite project with freeform commits.
talayash/agentrium
Stars: 49Claude CodeCodexDevelopment conventions and patterns for Agentrium (formerly claude-terminal). TypeScript Vite project with freeform commits.
talayash/agentrium
Stars: 49Claude CodeCodexOKX Agentic Wallet — the single skill for the user's wallet and on-chain execution. Use it whenever the user wants to operate their wallet or execute an on-chain action, including: login & accounts, balance / holdings, wallet address / deposit / receive, send / transfer, contract calls (approve / deposit / withdraw), transaction history & status, message signing, wallet export & policy; pay gas with a stablecoin (Gas Station, Solana); swap / trade / buy / sell / convert, get a quote; cross-chain bridge & track arrival; limit orders (buy dip / take profit / stop loss / buy above) plus cancel / list / resume them; broadcast / gas / simulate / track a transaction; look up any public address's holdings; security scanning (token / honeypot 蜜罐 / 貔貅, DApp phishing, tx & signature checks, approvals); audit log. Once matched, follow this skill's Intent Routing to dispatch to the exact action.
internet-court/internet-court-skill
Stars: 7.1kClaude CodeCodexWork with the QStash JavaScript/TypeScript SDK for serverless messaging, scheduling. Use when publishing messages to HTTP endpoints, creating schedules, managing queues, verifying incoming messages in serverless environments.
upstash/qstash-js
Stars: 271Claude CodeCodexCreate new Cebian skills, edit or improve existing ones, scaffold multi-file skill packages, and validate them against the agentskills.io specification. Use when the user wants to author, refactor, or debug a skill (including questions like "why isn't my skill firing"), declare metadata.permissions for scripts that call chrome.* APIs or inject code into pages, or rewrite a description for better trigger accuracy.
maotoumao/Cebian
Stars: 185Claude CodeCodexDiscover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.
rse/ase
Stars: 77Claude CodeCodexEdit Source Code: Use when the user wants to "edit" the code base in one shot from a query or a bare analyzer issue id like "P1", fusing crafting, refactoring, and resolving with optional grilling, verification, looping, and Git worktree isolation.
rse/ase
Stars: 77Claude CodeCodexExplains code with WHAT, WHY, ANALOGY, DIAGRAM, CRUXES, and GOTCHAS. Use when you want to know how code works or when the user asks "how does this work?"
rse/ase
Stars: 77Claude CodeCodexDistill a provided document into a flat, importance-ranked list of its key points, each with a salience rank, a rationale, and a verbatim line-cited evidence snippet. Use when the user wants to "distill", "summarize the key points", or "extract the essence" of a document or pasted text.
rse/ase
Stars: 77Claude CodeCodexMatch a free-text intent against the accumulated help of all ASE skills, generate all adequately fitting `/ase:ase-xxx-xxx` commands -- ranked best-fitting first, each with concrete options and arguments -- and let the user execute one of them, refine the intent, or cancel. Use when the user knows what they want but not which skill or flags realize it, or mentions "intent" or requests "help".
rse/ase
Stars: 77Claude CodeCodexShow the manual page of an ASE skill, addressed by its full name, by any abbreviation of it, or by a description of its purpose, and list the entire skill catalog when no name is given. Use when the user wants the "manual", "man page", "manpage", or "help" of a particular ASE skill, or asks what a certain `ase-xxx-xxx` skill does.
rse/ase
Stars: 77Claude CodeCodexCollaboratively brainstorm a topic by diverging on ideas, converging through clustering and scoring, and distilling a shortlist with a recommended direction. Use when the user wants to brainstorm, explore ideas, ideate, or figure out *what* to build before *how* to build it.
rse/ase
Stars: 77Claude CodeCodexList, get, set, or delete the layered ASE configuration values across the user/project/task/session scope chain. Use when the user wants to "configure" ASE, or to inspect or change a configuration key like `agent.persona`, `agent.guidance`, `project.boxing`, or `project.task.lifecycle`.
rse/ase
Stars: 77Claude CodeCodexChallenge a thesis by playing "Devil's Advocate" (Latin: "Advocatus Diaboli"). Use when the user wants a thesis or statement relentlessly challenged or criticised.
rse/ase
Stars: 77Claude CodeCodexExplain a topic in "Explain Like I'm 5" (ELI5) style, optionally grounded in Internet/Web facts. Use when the user wants a topic explained in a very simple, child-friendly way, or mentions "eli5" or "explain like I'm 5".
rse/ase
Stars: 77Claude CodeCodexEvaluate alternatives through a weighted multi-criteria decision matrix. Use when the user calls for the *evaluation* of *alternatives*, wants to *compare* things, or asks what the best is from a list of choices.
rse/ase
Stars: 77Claude CodeCodexMint an identifier or a name of a requested type out of a free-text hint: a UUID, a SHA-1 digest, a NanoId-style hash, a constant, variable, function, or class identifier, a path component, or a product-like name. Use when the user wants an identifier, id, symbol, slug, or name "minted", "coined", "derived", or "generated" from a description.
rse/ase
Stars: 77Claude CodeCodexDetermine the conceptual proximity of a topic -- its parent topic, its most relevant sibling topics, and its most relevant child topics -- optionally grounded in Internet/Web facts and optionally navigable in an interactive loop. Use when the user wants to explore the conceptual neighborhood of a topic, or mentions "proximity" or "related topics".
rse/ase
Stars: 77Claude CodeCodexFind quotes for a set of topic keywords and place them into a 2x2 matrix, spanned by the presence of an author/origin and by the literal containment of a keyword, optionally grounded in Internet/Web facts and optionally widened to the conceptual neighborhood of the topic. Use when the user wants "quotes", "sayings", "aphorisms", or "citations" on a topic.
rse/ase
Stars: 77Claude CodeCodexBuild the strongest possible case for a thesis by playing "Steelman" (Latin spirit: "Advocatus Dei"). Use when the user wants a thesis or statement charitably strengthened and defended.
rse/ase
Stars: 77Claude CodeCodexGenerate a new agent tool skill, written in the style of ASE skills, which orchestrates a workflow of sequential actions, parallel actions, sub-agent calls, and skill calls. Use when the user wants to "generate a skill", create a "workflow", "orchestrate" or "chain" multiple ASE skills, or automate a recurring multi-step procedure.
rse/ase
Stars: 77Claude CodeCodexUpdate ChangeLog entries in CHANGELOG.md files. Use when the user wants to "add a changelog entry", or to "update", "complete", or "consolidate" the "changelog", "ChangeLog", or "CHANGELOG.md", e.g. before committing or releasing.
rse/ase
Stars: 77Claude CodeCodexDetermine commit message for staged Git changes. Use when the user asks to "give", "write", "craft", "suggest", or "propose" a "commit message", or wants to know how to "describe" or "phrase" the staged changes for a commit.
rse/ase
Stars: 77Claude CodeCodexSummarize the currently staged Git changes as a human-readable, intent-grouped narrative. Use when the user wants a concise and brief report of what changed and why. Optionally can check the diff for intent coherence and show a risk and blast radius report.
rse/ase
Stars: 77Claude CodeCodexDissect the current Git change set, treated as an epic, domain-wise and logically into cohesive parts and materialize each part in its own dedicated Git WorkTree. Use when the user calls to "dissect", "split", "break up", or "decompose" a large change set into atomic, separately committable parts.
rse/ase
Stars: 77Claude CodeCodexMerge a Git source branch, including its still uncommitted changes, into a target branch through a regular merge, a rebase with fast-forward, or a squash merge, resolving merge conflicts semantically, check that the source branch landed, and emit a MERGED, CONFLICT, or FAILED verdict. Use when the user calls to "merge", "integrate", or "land" a branch.
rse/ase
Stars: 77Claude CodeCodexResolve the Git merge conflicts of a working directory -- of an in-progress merge, rebase, cherry-pick, revert, stash apply, or of conflict markers left by patch -- carefully and semantically, never losing any change, escalate unresolvable hunks as-is, continue the in-progress operation, and emit a RESOLVED, PARTIAL, NONE, or FAILED verdict. Use when the user calls to "resolve" or "fix" merge conflicts.
rse/ase
Stars: 77Claude CodeCodexStage only the part of the current Git working copy changes which belongs to a topic, to the last `CHANGELOG.md` entry, to the last turn, or to the entire session, by picking and, if necessary, splitting hunks, check that the staged state builds on its own, and optionally chain into ChangeLog updating and commit message crafting. Use when the user calls to "stage" only a part of the changes, like "the hunks related to" a topic or "the last turn".
rse/ase
Stars: 77Claude CodeCodexDerive a new task plan from a Git change set -- the staged changes (or, with `--unstaged`, the unstaged and untracked changes, with `--branch`, a branch against its base, or, with `--commit`, a single commit) -- optionally narrowed to a scope topic, by filling its SPECIFICATION (WHAT), DESIGN (HOW), and VERIFICATION (WHEN) sections (or only the focused ones), so that a re-implementation of the task, e.g. after an export to a foreign issue tracker, yields a similar change set. Use when the user wants a change set, branch, or commit "turned into", "described as", or "reverse-engineered into" a "task", "plan", or "issue".
rse/ase
Stars: 77Claude CodeCodex