Explore skills
Search every indexed skill by name, description, repository or instructions, then narrow the results.
Showing 14161–14190 of 15126 skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| ase-sync-importrse/aseImport information from foreign sources into a set of artifact kinds (the target), generating or updating them to reflect the imported information. Use when the user wants to "import", "ingest", or "bring in" external sources like files, URLs, or pasted text into artifacts like SPEC, CODE, DOCS, TASK, INFR, or OTHR. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-sync-reconcilerse/aseReconcile one set of artifact kinds (the target) to reflect the current state of another set of artifact kinds (the source), while optionally honoring a filtering hint. Use when the user wants to "reconcile", "sync", "align", or "update" artifacts like SPEC, CODE, DOCS, TASK, INFR, or OTHR against each other. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-assignrse/aseAssign the current or given task plan to oneself or to somebody else, with assigning it to oneself tracking the AI usage (time, tokens, and costs) of the session until the task is given back, which adds the accumulated usage to the usage attachment of the task. Use when the user wants to "assign", "take", "pick up", "give back", "hand over", or "unassign" the "task" or "plan". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-condenserse/aseCondense the current or given task plan by compressing its wording. Use when the user calls to "condense", "compress", "shrink" or "shorten" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-deleterse/aseDelete the current or given task plan. Use when the user calls to "delete", "remove" or "clear" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-dissectrse/aseDissect the current or given task plan, treated as an epic, domain-wise and logically into cohesive parts and materialize each part as its own separate task plan. Use when the user calls to "dissect", "split", "break up", or "decompose" a large "task" or "plan". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-editrse/aseIteratively edit and refine a named plan for a task through a conversational loop. A new plan is optionally composed along the chosen one of several proposed crafting, refactoring, resolution, or specification approaches. Each round, the current plan is shown and the user is asked whether to keep refining, mark the plan as done, or proceed to the implementation or draft. Use when the user wants to plan a task purely through chat-driven refinement, or wants a plan to "craft" a new feature, "refactor" the code base, or "resolve" a problem (also from a bare analyzer issue id like "P1"). | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-estimaterse/aseEstimate the effort of the current, given, or all unestimated task plans as T-shirt sizes (XS, S, M, L, XL) of expected human time, and store it in the "Effort:" frontmatter key, or calibrate the estimation against the actual human time of the finished tasks. Use when the user wants to "estimate", "size", or "gauge the effort" of a "task" or "plan", or to "calibrate" the effort estimation. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-grillrse/aseInterview the user relentlessly about the task plan until reaching a shared understanding, resolving each branch of the question decision tree. Use when the user wants to stress-test a plan, get grilled on their plan, or mentions "grill me" or "grill plan". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-idrse/aseGet or set unique task id <id>. Use when user requests to work on a certain task or wants to know what the current task is. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-implementrse/aseImplement current or given task plan, optionally as an implementation draft attachment only. Use when the user calls to "implement", "realize", "draft", "dry-run", or "test-drive" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-integraterse/aseIntegrate the change set or implementation draft of the current or given task plan into its target. Use when the user calls to "deliver" or "apply" the change set or draft of the "task" or "plan". For merging a plain Git branch, use `ase-repo-merge` instead. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-listrse/aseList all available task ids. Use when user wants to see all tasks. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-rebootrse/aseReboot the current or given task plan by re-creating it from scratch. Use when the user calls to "reboot", "recreate" or "refresh" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-renamerse/aseRename the current or given task plan. Use when the user calls to "rename", "move" or "relabel" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-researchrse/aseResearch a topic in depth for the current or given task plan, by combining Internet/Web search with a grounding in the source artifacts of the project, and append the resulting research report to the "research" attachment of the task, optionally refining the plan by its recommendations. Use when the user wants to "research", "investigate", or "look into" a topic for a "task" or "plan". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-statusrse/aseGet or set the lifecycle status of the current or given task plan. Use when the user wants to know or change the "status" or "state" of the "task" or "plan", e.g. to "close", "shelve", "cancel", or "re-open" it. | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| ase-task-viewrse/aseView current or given task plan. Use when the user calls to "view", "show" or "see" the "task", "plan", "spec", or "specification". | Stars: 76 | Updated | Claude CodeCodex | Unverified | Install |
| brainstormoprogramadorreal/optimus-claudeRuns a structured design conversation — clarifies intent, proposes 2-3 approaches with trade-offs, iterates the design — and writes a user-approved engineering spec to docs/specs/ that /optimus:tdd auto-detects. No implementation happens until the spec is approved. With the scaffold argument, creates docs/product/ steering skeletons instead (never overwrites, authors no content). Recommends /optimus:init first. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| code-reviewoprogramadorreal/optimus-claudeReviews local changes, an open PR/MR, or a branch diff for bugs, security issues, and violations of the project's own coding guidelines, through review lenses applied inline on a small diff or in parallel agents on a larger one. Excludes style and linter-catchable issues. Read-only: applies fixes or posts PR/MR comments only on explicit approval. For an iterative auto-fix loop, use /optimus:deep review. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| commitoprogramadorreal/optimus-claudeStages, commits, and optionally pushes local changes with a Conventional Commits message — always previews and confirms first, and offers a feature branch on protected branches. Modes: "suggest" proposes a message without committing (read-only); "branch [description]" creates and switches to a conventionally named branch, never committing or altering local changes. Multi-repo aware. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| deepoprogramadorreal/optimus-claudeRuns an iterative auto-fix loop on a chosen target — review, refactor, or coverage — dispatching the base skill into fresh subagent contexts per iteration, applying fixes automatically without per-change approval, running tests with bisection on failure, and checkpoint-committing until convergence or the cap. Requires /optimus:init and a test command in .claude/CLAUDE.md. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| dreamoprogramadorreal/optimus-claudePrunes and consolidates the project's auto-memory to keep it minimal — deletes stale, wrong, or redundant memories, merges overlapping ones into existing files, and trims the index. Strong bias against growth: never creates new memory files and never stores new facts. Verifies staleness against the current codebase, then presents the plan and asks before deleting. Requires Claude Code auto-memory; run periodically after heavy stretches of work. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| gauntletoprogramadorreal/optimus-claudeRuns a Gauntlet Loop: turns an ambitious goal into a builder/critic prompt judged against a concrete quality bar, confirms with the user, then leads the run until the output beats the bar or the user stops it — or exports a paste-ready /goal prompt for a fresh session. Use for long-horizon goals with an inspectable reference. Long-running; spawns many subagents, edits project files, and commits and pushes finished pieces to a feature branch. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| handoffoprogramadorreal/optimus-claudeCompacts the current conversation into one self-contained, tool-agnostic handoff document at docs/handoffs/<slug>.md so any fresh agent or teammate can resume the work from that file alone. References pushed artifacts by path or URL, inlines anything not on the remote, and redacts secrets and PII. Re-running on an existing handoff offers enhance or overwrite. Writes one project artifact and, when needed, a private scratchpad backup; never commits. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| how-to-runoprogramadorreal/optimus-claudeGenerates or updates a project's HOW-TO-RUN.md — one verified document teaching a new developer to set up their environment and run the project locally. Detects toolchain, source dependencies, external services, and env config via a read-only agent; audits an existing file against actual project state and offers a display-only guided walkthrough. Never runs setup commands; writes only HOW-TO-RUN.md. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| initoprogramadorreal/optimus-claudeBootstraps a project for Claude Code or Codex — generates routed project guidance from detected structure, reconciles existing docs, and offers test infrastructure. Claude Code can also install formatter hooks. Writes .claude/, CLAUDE.md, AGENTS.md and subproject docs/; may append to README/.gitignore and, with approval, install dev dependencies. Preserves existing guidance through review and recorded ownership. Use for initial setup or upgrades. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| jiraoprogramadorreal/optimus-claudeFetches a JIRA issue via a configured MCP server and distills it into a structured task file at docs/jira/<KEY>.md that downstream skills auto-detect. Analyzes the codebase to surface missing criteria, scope, and risks; optionally writes an analysis comment or implementation tickets back to JIRA after explicit confirmation. Re-runs reconcile the local file instead of regenerating. Guides MCP setup if none is configured. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| paper-initoprogramadorreal/optimus-claudePrepares durable context for implementing and reproducing a paper from a URL, PDF, DOI, or arXiv id: sources, source-linked requirements, empirical acceptance criteria, uncertainties, scope, and data provenance under paper/. Downloads sources and datasets (into data/) and updates .gitignore, .gitattributes, and README routing. Context only: writes no implementation code and sets up no project stack. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |
| permissionsoprogramadorreal/optimus-claudeConfigures Claude Code permissions for low-prompt work inside a project; changes nothing under Codex. Creates or merges allow/deny rules in .claude/settings.json and installs a PreToolUse hook gating out-of-project writes and deletes, precious untracked files, and history-changing git on protected branches. Writes only under .claude/, including an ownership record. Use after /optimus:init or standalone. | Stars: 75 | Updated | Claude CodeCodex | Unverified | Install |