Loading...
Loading...
Found 3,053 Skills
World-class OKR coaching and sparring partner that provides sharp, practical criticism for OKR drafts. Use when creating, reviewing, or refining OKRs to ensure strategic alignment, measurability, and executability.
Automation skill for designing, verifying, and improving auth, cost, logging, and security compliance based on the internal AI tool mandatory implementation guide (P0/P1). Supports the full lifecycle of RBAC design, Gateway principles, Firestore policy, behavior logs, cost transparency, and the criteria verification system.
Smoke test for alicloud-network-cdn. Validate minimal authentication, API reachability, and one read-only query path.
Smoke test for alicloud-ai-content-aimiaobi. Validate minimal authentication, API reachability, and one read-only query path.
Provides active execution protocols to rigorously audit how code, directory structures, and agent actions comply with the authoritative ecosystem specs. Trigger when validating new skills, plugins, or workflows.
This skill should be used when the user asks to "create a skill", "write a new skill", "add a skill", "SKILL.md format", "skill frontmatter", or needs guidance on skill structure, progressive disclosure, or OpenCode skill development.
Pre-flight check before pushing to production. Catches TypeScript errors, accidentally staged secrets, pending migrations, and hygiene gaps before they hit live users.
Perses-aware code review: check Go backend against Perses patterns, React components against Perses UI conventions, CUE schemas against plugin spec, and dashboard definitions against best practices. Dispatches appropriate sub-reviewers. Use for "review perses", "perses pr", "perses code review". Do NOT use for general Go/React review without Perses context.
Fetch PR feedback from all GitHub sources and validate every comment before acting. Use when user needs to process PR review comments, address reviewer feedback, or triage pull request discussions. Use for "review comments", "PR feedback", "address reviews", "address feedback", or "what did reviewers say". Do NOT use for creating new PRs, code review of local changes, or general code analysis without an existing PR.
Audit applications against your platform engineering constitution. Use when validating that code, configurations, and deployments align with organizational infrastructure standards.
Discuss and brainstorm a spec-driven change from a rough idea, then propose a change name and, after explicit confirmation, generate the same five proposal artifacts as spec-driven-propose.
Evaluate the output of a journey-builder run, identify instruction gaps, and edit the project root AGENTS.md (or add pitfalls to the gist) to fix those gaps. Does NOT modify the journey-builder skill itself.