Loading...
Loading...
Found 6,254 Skills
Assess organization's digital transformation readiness. Evaluate data culture, technology adoption, and process maturity.
Generate a requirements-quality checklist for an OpenSpec change and run it against the proposal/design/tasks/delta — validating completeness, clarity, consistency, and testability BEFORE you approve the spec. Modeled on GitHub Spec-Kit's /checklist. Use when reviewing a spec at the human approval gate, or before launching implementation, to catch under-specified requirements early.
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
Lance des dés pour jeux de rôle (Basic Fantasy RPG). Supporte d4, d6, d8, d10, d12, d20, d100. Notation standard comme 2d6+3, 4d6kh3 (keep highest). Avantage et désavantage. Utilisez pour tout jet de dé en session de JdR.
Use to coordinate approvals, communications, and accountability across teams for feedback programs.
Aptos GF(3) Society Skill
Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.
Use when you need to turn selected modules (P0 priority first) into single-page module SSOT at the path `.aisdlc/project/components/{module}.md`, and build authoritative entries for API/Data contracts, invariant summaries, evidence entries and structured Evidence Gaps in the same page to meet the DoD gate requirements of Discover.
Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator
When the user wants to create Pinterest Pins, optimize Pin descriptions, or grow Pinterest presence. Also use when the user mentions "Pinterest," "Pin," "Pinterest SEO," "Pinterest description," "Pinterest board," or "Pinterest marketing."
CLI and TUI tool that explains why processes, services, and ports are running by tracing causality chains across supervisors, containers, and shells.
4-phase code review methodology: UNDERSTAND changes, VERIFY claims against code, ASSESS security/performance/architecture risks, DOCUMENT findings with severity classification. Use when reviewing pull requests, auditing code before release, evaluating external contributions, or pre-merge verification. Use for "review PR", "code review", "audit code", "check this PR", or "review my changes". Do NOT use for writing new code or implementing features.