Explore skills
Showing 65791–65820 of 71445 skills
Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).
srid/smriti
Stars: 0Claude CodeCodexIterative measurement-driven improvement loop. Measure, profile, mutate, re-measure, commit. Works for performance, bundle size, complexity, test coverage — anything quantifiable. Use when the user wants to systematically improve a metric through repeated cycles of profiling and targeted changes.
srid/smriti
Stars: 0Claude CodeCodexEnter talk mode — conversation and research, no repo changes. ONLY invoke when the user explicitly types `/talk` or `$talk`; never auto-select from a natural-language question or design discussion.
srid/smriti
Stars: 0Claude CodeCodexCheck and process messages from autonomous AILANG agents. Use when starting a session, after agent handoffs, or when checking for completion notifications.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodexMaintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodexTrack and optimize agent specialization during methodology development. Use when agent specialization emerges (generic agents show >5x performance gap), multi-experiment comparison needed, or methodology transferability analysis required. Captures agent set evolution (Aₙ tracking), meta-agent evolution (Mₙ tracking), specialization decisions (when/why to create specialized agents), and reusability assessment (universal vs domain-specific vs task-specific). Enables systematic cross-experiment learning and optimized M₀ evolution. 2-3 hours overhead per experiment.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodexAnalyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodexUse this skill when creating or updating a pull request in the TTA.dev repository. Covers PR title format, description template, review expectations, and pre-submit checklist. Invoke when the user says "create a PR", "open a pull request", "submit my changes", or "make a PR".
theinterneti/TTA.dev
Stars: 0Claude CodeCodexUse this skill when making git commits in the TTA.dev repository. Enforces Conventional Commits format and pre-commit quality checks. Invoke when the user says "commit", "git commit", "save changes", "commit my work", or asks how to commit code.
theinterneti/TTA.dev
Stars: 0Claude CodeCodexAsk which skill or flow fits your situation. A router over the skills in this repo.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexTest-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexTurn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexTeach the user a new skill or concept, within this workspace.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexReference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
MaksymilianCzadowski/skills
Stars: 0Claude CodeCodexUse when reviewing code for security vulnerabilities, threat-modelling a new feature, implementing authentication or authorization, handling user input, hardening dependencies or CI/CD against software-supply-chain compromise, or auditing a codebase against the current OWASP Top 10 (2025, with the 2021 mapping retained). Covers broken access control (incl. SSRF), security misconfiguration, software supply chain failures, cryptographic failures, injection (SQL, NoSQL, command, LDAP, XSS), insecure design, authentication failures, software/data integrity failures, security logging and alerting failures, and mishandling of exceptional conditions (fail-open error paths, error leakage). Do NOT use for general code review (use `code-review` for the holistic per-PR pass), for chasing a known production bug (use `debugging`), for defending an LLM against prompt/RAG injection or agent-tool-authority abuse (use `prompt-injection-defense`), or for writing a security policy doc (use `documentation`).
jacob-balslev/skill-graph
Stars: 3Claude CodeCodexReplace with description of the skill and when Claude should use it.
cianfhoghlaim/cianchosaint
Stars: 2Claude CodeCodexAdd new Agent templates to the meta-agent-skills framework.
diegosouzapw/awesome-omni-skill
Stars: 67Claude CodeCodex3D game development principles. Rendering, shaders, physics, cameras.
jacksonemmerich/farmapub
Stars: 0Claude CodeCodexExpert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing ...
jacksonemmerich/farmapub
Stars: 0Claude CodeCodexThis skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", ...
jacksonemmerich/farmapub
Stars: 0Claude CodeCodexAutomate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.
jacksonemmerich/farmapub
Stars: 0Claude CodeCodexCRITICAL: MUST run for EVERY message. Detects agent, complexity, AND model automatically. Always runs FIRST.
jacksonemmerich/farmapub
Stars: 0Claude CodeCodexBuild Azure AI Foundry agents using the Microsoft Agent Framework Python SDK (agent-framework-azure-ai). Use when creating persistent agents with AzureAIAgentsProvider, using hosted tools (code int...
jacksonemmerich/farmapub
Stars: 0Claude CodeCodexA hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
jacksonemmerich/farmapub
Stars: 0Claude CodeCodexSystematic improvement of existing agents through performance analysis, prompt engineering, and continuous iteration.
jacksonemmerich/farmapub
Stars: 0Claude CodeCodexOptimize multi-agent systems with coordinated profiling, workload distribution, and cost-aware orchestration. Use when improving agent performance, throughput, or reliability.
jacksonemmerich/farmapub
Stars: 0Claude CodeCodex