Explore skills
Showing 56551–56580 of 71536 skills
Design and change REST, GraphQL, RPC, and webhook contracts and the backend services and jobs behind them: validation, authorization scope, error semantics, pagination, idempotency, rate limits, retries, timeouts, versioning, and contract tests. Use for any endpoint, external integration, worker, or queue consumer.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexTactics for large repositories, noisy tool output, long sessions, and token pressure: search before reading, read ranges not files, keep logs and generated output out of context, never reread unchanged files or rerun unchanged passing checks, prefer deterministic scripts. Use when context volume materially affects execution quality; never reduces necessary reasoning, security, or verification.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexSchema design, migrations, transactions, indexes, query behavior, backfills, and tenant isolation or RLS. Treats every schema or migration change as high risk because deployed data already exists. Use for SQL, ORMs, data models, migration strategy, query performance, or data-integrity questions.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexDecide whether subagents, parallel agents, or agent teams are justified and, if so, delegate safely: one agent unless work is bounded, independent, and clearly owned; explicit outcome, ownership, constraints, and return format per worker; the integrating agent owns final correctness, security review, and verification. Use whenever delegation or parallel execution is being considered.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexCI/CD pipelines, containers, infrastructure as code, cloud services and IAM, deployment and rollout strategy, rollback, backups and restore, monitoring and alerting, and reliability controls. Use for any workflow, Dockerfile, Terraform, Kubernetes, cloud, deployment, or operations change. Production and infrastructure mutations require explicit authorization.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexDocument implemented, verified reality in the repository's existing source of truth: READMEs, API references, ADRs, runbooks, migration notes, changelogs, and code comments. Use when documentation must be written, updated, or checked for drift; never document unverified capabilities.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexImplement visual frontend work with an intentional design direction: inspect the existing design system and tokens, design mobile and desktop deliberately, implement every state (loading, empty, error, disabled, overflow, permission-denied), protect hierarchy and layout stability, and verify rendered behavior. Always composes with accessibility-quality. Use for UI implementation, styling, layout, and component work.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexKeep history safe and meaningful: inspect status and diff before and after editing, preserve unrelated user work, scope commits logically, write accurate messages, resolve conflicts by understanding both sides, and never rewrite shared history, force-push, or discard work without explicit authorization. Use for commits, branches, merges, rebases, and PR hygiene.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexSelect tests by risk, design strong regression and boundary tests, handle flaky suites, and run the completion gate with evidence: exact command, result, scope, and every skipped or blocked check. Use when choosing what to test, judging whether work is done, or producing release evidence. Never weaken a failing test to get green.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexMake product flows clear and recoverable: primary action and next step obvious, forms with clear labels, validation timing, actionable errors, preserved input on failure, consistent navigation and terminology, and no hidden or surprising destructive actions. Use for user flows, forms, navigation, onboarding, dialogs, and interaction design.
AL-JANEF/janef-forge
Stars: 1Claude CodeCodexThis skill should be used when the user wants to "dca into" a token, "buy X every day", set up a "recurring buy", "dollar cost average" into an asset, "schedule a buy", or "auto-buy on a dip". Buys a fixed amount into a token on a schedule, optionally only when a condition holds (for example only when ETH is below a price threshold). The host agent's scheduler wakes the skill on a cadence; each wake is one self-contained run.
Catalyst-Astro/Catalyst-Blockchain-Structural-Token-
Stars: 0Claude CodeCodexThis skill should be used when the user wants to "dca into" a token, "buy X every day", set up a "recurring buy", "dollar cost average" into an asset, "schedule a buy", or "auto-buy on a dip". Buys a fixed amount into a token on a schedule, optionally only when a condition holds (for example only when ETH is below a price threshold). The host agent's scheduler wakes the skill on a cadence; each wake is one self-contained run.
Catalyst-Astro/Catalyst-Blockchain-Structural-Token-
Stars: 0Claude CodeCodexBuild, relaunch, and observe the Claudence menu bar app to verify a change end-to-end.
Mark-in-Motion/Claudence
Stars: 0Claude CodeCodexUse the skill to control and verify the code interface configuration of your model — how Simulink® model elements are represented in the generated C or C++ code. This includes — (1) specifying names, types (storage classes), and placement of variables that represent model elements (for example, making a model parameter tunable as a global extern variable); (2) specifying names, types, and placement of functions that represent model algorithms; (3) selecting the deployment type (Component, Subcomponent, or Automatic); (4) selecting the interface configuration type (data or service interface); (5) linking a shared Embedded Coder dictionary to a model; (6) creating Embedded Coder dictionary entries and setting their properties; (7) for service interface configuration — specifying service interface definitions, including sender, receiver, client, and server services. Items 1 and 2 can be set per element or as a category-wide default. Item 1 applies to GRT and ERT models; the rest to ERT models only.
zrwangems/dsh-zrwang-plugin
Stars: 2Claude CodeCodexCreate, populate, and manage safety analysis spreadsheets (FMEA, FHA, HARA, custom) and fault trees (FTA) in Safety Analysis Manager. Use when the user asks to perform FMEA, hazard analysis, fault tree analysis, safety analysis, or work with Safety Analysis Manager documents. Requires Simulink Fault Analyzer.
zrwangems/dsh-zrwang-plugin
Stars: 2Claude CodeCodexTests Simulink models using either ephemeral Gherkin-based tests (model_test) for quick validation or persistent tests (Simulink Test API) authored from requirements or behavioral specs. Requires Simulink Test.
zrwangems/dsh-zrwang-plugin
Stars: 2Claude CodeCodexDocumentation for just and justfile. This skill should be used before editing justfile or running just commands. TRIGGER when run just command, or edit justfile; or when about to write any `just ...` shell invocation in Bash, pueue, or scripts.
archibate/dotfiles-opencode
Stars: 109Claude CodeCodexIndependently verify a suspected Ouros security finding. Use after another agent reports a vulnerability or suspicious behavior, before severity is finalized, an issue is opened, or a fix is proposed as security-critical.
Ouros-App/ouros-skills
Stars: 0Claude CodeCodexAudit Ouros AI, MIDAS, MCP and tool-calling security. Use when reviewing prompt-injection resistance, tool authorization, cross-user/thread isolation, MCP boundaries, guardrails, model-controlled arguments, or whether AI behavior can exceed the authenticated user's privileges.
Ouros-App/ouros-skills
Stars: 0Claude CodeCodexCoordinate an authorized security audit of Ouros repositories and QA/local services. Use when the user asks for a broad security review, red-team-style assessment, attack-surface audit, pre-release security pass, or autonomous security campaign across multiple Ouros components.
Ouros-App/ouros-skills
Stars: 0Claude CodeCodexRun authorized, non-destructive security tests against Ouros local or QA services. Use for runtime verification of auth, authorization, API, business-logic or configuration hypotheses when the environment must be left clean and stable afterward.
Ouros-App/ouros-skills
Stars: 0Claude CodeCodexForce unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexFlip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexSpot patterns appearing in 3+ domains to find universal principles
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexTest at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexFind one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexForce unrelated concepts together to discover emergent properties - "What if we treated X like Y?"
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexFlip core assumptions to reveal hidden constraints and alternative approaches - "what if the opposite were true?"
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexSpot patterns appearing in 3+ domains to find universal principles
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodexTest at extremes (1000x bigger/smaller, instant/year-long) to expose fundamental truths hidden at normal scales
DangQuangSE/team-development-skills
Stars: 19Claude CodeCodex