Explore skills
Showing 24661–24690 of 77079 skills
Request write permission from the user before making file changes. MUST be invoked before any write attempt when the write gate is closed. Creates scoped approval via AskUserQuestion + TaskCreate, opens the write gate, and closes it when work is done. Triggers: write hook blocks an edit, agent is about to write files outside .craft/, agent needs to modify project source files. This skill requires user approval 100% of the time - never bypass AskUserQuestion.
drobins25/craft
Stars: 73Claude CodeCodexInteractive browser automation via playwright-cli. Use when you need to navigate a site, click elements, fill forms, take snapshots, or triage a live app.
drobins25/craft
Stars: 73Claude CodeCodexThis skill should be used when the user asks to "brainstorm", "explore options", "get creative", "what if we...", or selects "Let's get creative" during story or cycle creation. NOT for a bare vague feature idea where generating options would mean inventing the premise first - that routes to /craft:riff (riff first, options after). Generates 3-4 creative options with trade-offs, visual direction for UI stories, and wireframes.
drobins25/craft
Stars: 73Claude CodeCodexUse this skill when the user wants to discover, define, or refine their product's aesthetic identity. Triggers on "what should this feel like?", "help me figure out the vibe", "something feels off visually", "I want it to feel like [X]", "define the visual language", or when a project has no established design direction. This is the art director skill - it helps users articulate something they can feel but can't name. Also handles quick cohesion checks when the orchestrator needs one during cycle planning.
drobins25/craft
Stars: 73Claude CodeCodexThis skill should be used when the user says "lock it", "go with that", "approved", "that's the standard", or explicitly establishes a project-wide pattern like "from now on all forms should use this approach". Formalizes approved decisions into locked standards that the system enforces going forward. Not needed for story-scoped decisions — only for project-wide patterns.
drobins25/craft
Stars: 73Claude CodeCodexThis skill should be used when the user asks to "plan chunks", "break this down", "plan the implementation", or when a story has status planning and needs implementation details before building. Required before any story can be implemented. Turns a story into a chunk-by-chunk build plan with file lists, the contracts chunks share, named tests and risks. Supports parallel planning of multiple stories via batch mode.
drobins25/craft
Stars: 73Claude CodeCodexThis skill should be used when validate-chunk reports errors or failures, when the user asks to "fix these errors", "resolve validation issues", "refine this chunk", or when specific build, lint, or type errors need surgical fixes. Makes precise, targeted edits to resolve specific validation issues without over-engineering.
drobins25/craft
Stars: 73Claude CodeCodexThis skill should be used when validate-chunk reports test failures specifically, when the user says "tests are failing", "figure out what's wrong with the tests", "fix the failing tests", or when test assertions don't match expected output after chunk implementation. Triages whether the test or the implementation is wrong and fixes the correct one.
drobins25/craft
Stars: 73Claude CodeCodexEnforcement layer for chunk and story validation. Invokes the chunk-validator agent (haiku), enforces the verdict, routes failures to refine-chunk or test-fix, captures CLI learnings. The orchestrator invokes this skill — never the agent directly.
drobins25/craft
Stars: 73Claude CodeCodexUse when an already-running 02-DOCS/ wiki needs gardening judgment — what is worth capturing (default: nothing), where a loose note belongs, whether to split a bloated article or merge near-duplicates, how to link orphans back in, and what retires to _archive (never delete). NOT building or sweeping the wiki engine itself (that is `harness`).
ericrisco/rsc-harness
Stars: 622Claude CodeCodexFile one feature request per Break-down line of a merged design and attach each one as a sub-issue of the proposal. Use when asked to break a design down, to file or create the sub-issues or child issues of a design, or to split a merged design into issues.
Kinference-AI/kinference
Stars: 111Claude CodeCodexWrite a design document under design/ from design/TEMPLATE.md for a proposal issue that a maintainer labelled needs-design. Interviews the user, researches prior art in fresh contexts, has a fresh context attack the draft, and commits it on a branch when asked. Use when asked to design, propose or plan a change that a maintainer sent to design, or to write a design document.
Kinference-AI/kinference
Stars: 111Claude CodeCodexDraft a bug report or a feature request for this repository from its issue forms, since gh issue create skips them, and file it when the user approves the draft. Use when asked to file, write, report or open a bug, a feature request, a proposal or an issue.
Kinference-AI/kinference
Stars: 111Claude CodeCodexCheck the current branch against the contribution workflow and draft a pull request title and description in the shape that CONTRIBUTING.md and the template require, for an implementation, a design or a sub-issue, then open or update the pull request when asked. Use when asked to open, write, draft, update or fix a PR or a pull request description, to answer review, or to fold fixups.
Kinference-AI/kinference
Stars: 111Claude CodeCodexCreate user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
harperreed/dotfiles
Stars: 337Claude CodeCodexUse XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.
harperreed/dotfiles
Stars: 337Claude CodeCodexSwift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.
harperreed/dotfiles
Stars: 337Claude CodeCodexInstall Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
harperreed/dotfiles
Stars: 337Claude CodeCodexRemove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
harperreed/dotfiles
Stars: 337Claude CodeCodexA skill with no eval.yaml for testing discovery behavior.
dotnet/skills
Stars: 6.2kClaude CodeCodexDeprecated. Output schema generation moved to the apify-actor-development skill; prefer that skill whenever it is available.
apify/agent-skills
Stars: 2.5kClaude CodeCodexBuild and customize docs UI with @ariadocs/components — the Docs.* layout (sidebar, mobile nav, table of contents, page), the OpenAPI.* API reference parts, theming with --aria-* CSS variables, and MDX content components such as Callout, Tabs, Steps and Cards (which the package does not include). Use when the user wants to change a docs layout, add a mobile menu, hide or reorder parts of an endpoint page, theme the components, add callouts/tabs/steps/cards to MDX, or compose custom API reference pages. For loading MDX content use the `ariadocs-mdx` skill; for parsing OpenAPI specs and reference routes use `ariadocs-openapi`.
nisabmohd/aria-docs
Stars: 414Claude CodeCodexAdd MDX documentation pages to a React app with @ariadocs/mdx — read a folder of .mdx files, render pages (Server Components or client), frontmatter, table of contents, sidebar navigation from _meta.json, static paths, remark/rehype plugins, custom MDX components and untrusted MDX. Use when the user wants to set up docs pages, render MDX files or MDX from a CMS, build a docs sidebar or TOC, or migrate from @ariadocs/react. Covers Next.js (App and Pages Router), React Router (v7 and v8) and TanStack Start. For the UI (layout, sidebar, callouts) use the `ariadocs-components` skill; for API references use `ariadocs-openapi`.
nisabmohd/aria-docs
Stars: 414Claude CodeCodexBuild an API reference from an OpenAPI 3.0/3.1/3.2 spec with @ariadocs/openapi — parse and validate a spec from a file, URL or object, list operations, tags and schemas, build sidebar navigation and per-endpoint static paths, generate code samples, search, and handle untrusted specs. Use when the user wants an API reference, endpoint pages, a spec-driven sidebar, request code samples, or to read an OpenAPI spec in React. Covers Next.js (App and Pages Router), React Router (v7 and v8) and TanStack Start. For rendering and customizing the reference UI use the `ariadocs-components` skill.
nisabmohd/aria-docs
Stars: 414Claude CodeCodexBuild the Convex project from source. Use when a contributor wants to compile, test, or package Convex.
Convex-Dev/convex
Stars: 119Claude CodeCodexContinue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never treat another vendor's session ID as portable.
claude-world/director-mode-lite
Stars: 80Claude CodeCodexUse when developing in packages/agent-core-v2 (the DI × Scope agent engine) — adding or modifying a domain Service, choosing a LifecycleScope, wiring DI dependencies, splitting a domain across scopes, owning or migrating a config section, gating behavior behind an experimental flag, raising coded errors, working on the permission system, writing DI/Scope tests, porting business logic from agent-core (v1) to v2, triaging a main-branch commit against v2, or exposing a v2 domain over server-v2 while keeping the /api/v1 wire contract compatible with released clients. Self-contained guide organized by development stage (orient → design → implement → test → verify) plus align workflows for v1→v2 migration, main-branch commit triage, and server-v2 wire exposure; each file carries the rules, examples, and red lines for its step.
PyModel/pythinker-code
Stars: 29Claude CodeCodex以 AddressSanitizer(ENABLE_TEST_SANITIZE=ON)构建并运行 vlink-test 单元测试,复现 CI 的 ASan 门禁。用户要求"跑 asan"、"内存检测测试"、 排查 ci-test 的 sanitize 失败时使用。
thun-res/vlink
Stars: 112Claude CodeCodex构建并运行 vlink-bench 性能基准(showcase/quick/full 预设),生成 HTML/JSON 报告。用户要求"跑 bench"、"性能测试"、对比后端吞吐/延迟、 验证性能回归时使用。
thun-res/vlink
Stars: 112Claude CodeCodex用 gh CLI 触发/查看 GitHub CI/CD:手动 dispatch 工作流 (release/coverage/docker)、查看运行状态与失败日志、重跑失败 job. 用户要求"触发 CI"、"看流水线"、"重跑失败的 job"时使用;创建 dev 到 master 的 PR 使用 /pr,正式发版使用 /release.
thun-res/vlink
Stars: 112Claude CodeCodex