Explore skills
Showing 46681–46710 of 77104 skills
Canonical legend for expanding a `less than KEY_PROTOCOL_VALUEgreater than ` placeholder into a shell substitution based on the key-context artifact's `source` field, plus the mandatory `pnpm --silent` rule that keeps the resolved key out of logs and the display-the-key-name-before-CONFIRM disclosure. Referenced by every warp deploy/update skill that passes a `--key.protocol` flag.
recoil-labs/recoil-link
Stars: 0Claude CodeCodexagentskillexchange/skills
Stars: 65Claude CodeCodexagentskillexchange/skills
Stars: 65Claude CodeCodexagentskillexchange/skills
Stars: 65Claude CodeCodexagentskillexchange/skills
Stars: 65Claude CodeCodexCanonical entry skill whenever a shared change may need to reach sovereign node repositories. Routes package publication, exact package bumps, pinned workflows, fail-closed codemods, literal source ports, and node-owned product changes to separate knowledge atoms.
cogni-dao/cogni
Stars: 4Claude CodeCodexRedirect for requests phrased as node-template sync. Load node-sync-prs, which owns every supported path from shared change to sovereign node repository.
cogni-dao/cogni
Stars: 4Claude CodeCodexUse when implementing a code change, opening a code PR, or resuming its CI, flight, merge, or promotion. Routes delivery to the current node's contracts. Routes each work-item status to its lifecycle command. Explanations and knowledge-only contributions use their task-specific guidance.
cogni-dao/cogni
Stars: 4Claude CodeCodexUse before authoring or reviewing a Cogni knowledge entry with entryType html — a diagram, matrix or status grid for human review. Html is diagram-first, themed by the renderer, and nearly prose-free; anything an agent must recall stays a markdown text atom.
cogni-dao/cogni
Stars: 4Claude CodeCodexRun a multi-agent build session: the main session acts as manager — cutting a goal into units, spawning implementer, tester, and adviser subagents, and running the test-and-review loop to completion under anti-thrash guardrails.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexApply whenever writing or editing code in any language, even if comments are not explicitly requested. Enforces comment and documentation discipline: concise file headers, function docs in the language's native format, inline comments for non-obvious logic, and protection of existing comments. Not required during suggestion-only or discussion when no file is written.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexAudit the repository for comment coverage and bring under-commented source up to standard. Walks one file at a time, proposes comments per file for approval, and tracks progress to resume across sessions. Invoke with /comment-audit.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexUpgrade outdated dependencies one package at a time, with a changelog check for breaking changes and a test run between upgrades. Invoke with /dependency-upgrade; pass package names to limit scope.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexUse this skill whenever the user needs help choosing between programming technologies, libraries, frameworks, tools, patterns, or architectural approaches. Covers all programming domains. Trigger even if the user doesn't say "suggest" explicitly — any programming decision where options exist and verification matters should use this skill.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexImprove the visual design of the job tracker React frontend. Use when asked to improve, redesign, restyle, or enhance the UI in job-tracker-ui/.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexWrite documents in a plain, human voice and remove phrasing that reads as machine-generated. Use this skill EVERY time you produce a written artifact meant to be read by a person: READMEs, official documentation, design or planning docs, summaries, reports, proposals, release notes, changelogs, commit messages, GitHub issues, pull request descriptions, letters, emails, blog posts, and similar deliverables. Trigger it whenever the task is "write/draft/generate a doc" rather than answering a question in chat. Do NOT trigger it for direct conversational replies, inline explanations, or code. Run it in two passes: write the document, then re-read the finished draft and rewrite anything that signals a machine wrote it, presenting only the corrected version.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexCreate or reconcile a repository's labels from the preset in `labels.yml`. Writes labels only — never deletes, never touches labels outside the preset. Invoke with /label-setup.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexAt session end, write the one-file session baton (docs/session/baton.md): a high-level summary of what this session was about, the goal, and the single next task. Overwrites the file — no change lists, no task lists, no detail. Read-only on git; writes only the baton. Use `session-wrapup` for git state and progress.md.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexClose out a working session: update `docs/progress.md`, report uncommitted and unpushed work, and list the session's decisions and open threads. Read-only on git — never commits, stages, or pushes.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexApply whenever the task is diagnosing a bug, a failing test, or unexpected behavior — even if the user only says "fix it". Core rule: never fix what has not been reproduced. Not required for feature work, or when the user has already stated the cause and only wants the change made.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodexImprove the visual design of the job tracker React frontend. Use when asked to improve, redesign, restyle, or enhance the UI in job-tracker-ui/.
NagareNegishi/Job-Application-Tracker
Stars: 0Claude CodeCodex从规划到发布的 DeepSeek Harness 插件全流程指南,覆盖需求与形态决策、脚手架生成、业务实现、本地验证、发布准备和最终发布。Use when the user wants to plan, create, bootstrap, develop, verify, or publish a DSH plugin/extension, or asks how to build a DeepSeek Harness plugin end-to-end.
goatbroai/dsh-plugin-scaffold
Stars: 11Claude CodeCodexLazy senior dev mode for any coding task (write, refactor, fix, review): YAGNI, stdlib first, no unrequested abstractions. Not for non-coding requests.
amanpal3/Dr-SKILLs
Stars: 2Claude CodeCodexReview a diff for over-engineering. Finds what to delete: reinvented stdlib, needless deps, speculative abstractions. One line per finding.
amanpal3/Dr-SKILLs
Stars: 2Claude CodeCodexForces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
amanpal3/Dr-SKILLs
Stars: 2Claude CodeCodexWhole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.
amanpal3/Dr-SKILLs
Stars: 2Claude CodeCodexHarvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
amanpal3/Dr-SKILLs
Stars: 2Claude CodeCodexCode review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.
amanpal3/Dr-SKILLs
Stars: 2Claude CodeCodexExecutes Ralph autonomous build loops. Selects open user stories from prd.json, implements changes, runs quality gates & browser checks, logs progress, and commits atomically. Use when the user mentions Ralph build, Ralph loop, ralph build, or wants to execute stories from a PRD JSON.
amanpal3/Dr-SKILLs
Stars: 2Claude CodeCodexExecutes Ralph autonomous build loops. Selects open user stories from prd.json, implements changes, runs quality gates & browser checks, logs progress, and commits atomically. Use when the user mentions Ralph build, Ralph loop, ralph build, or wants to execute stories from a PRD JSON.
amanpal3/Dr-SKILLs
Stars: 2Claude CodeCodex