Loading...
Loading...
Found 21 Skills
Maintain repository integrity and documentation. Use for auditing structure, checking config validity, and reviewing inventory. Use proactively to validate the repository or sync documentation. Examples: - user: "Validate the repo" → run audit_repo.py - user: "Check agents" → run audit_repo.py, review errors - user: "Update documentation" → run sync_docs.py - user: "Check for issues" → run full audit
Guide for understanding and contributing to the awesome-game-security curated resource list. Use this skill when adding new resources, organizing categories, understanding project structure, or maintaining the README.md format consistency.
Keep Eve-compatible repos aligned with platform best practices and current manifest conventions.
Add a new skill to the LaunchDarkly agent-skills repo. Use when creating a new SKILL.md, adding a skill to the catalog, or aligning with repo conventions. Guides exploration of existing skills before creating.
Repository management strategies including branch strategies (Git Flow, GitHub Flow, trunk-based), monorepo patterns, submodules, and repository organization. Use when user needs guidance on repository structure or branching strategies.
Turn raw PM content into a compliant, publish-ready skill by choosing build/add paths, running conformance checks, and updating docs before commit.
Development workflows for the playwright-cli repository. Use when the user asks about rolling dependencies, releasing, or other repo maintenance tasks.
Check all READMEs for accuracy and consistency across the meta-repo
Maintain Go repositories with high-quality standards, adhering to CI/CD, linting, and agent-friendly best practices.
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
This skill should be used when a new ArcKit command has been added and documentation needs updating across the repository. Triggers: update documentation for new command, update command count, add command to README, update DEPENDENCY-MATRIX, update docs/index.html, new command documentation checklist, update all docs for new command, add command to dependency matrix, update command tables, sync documentation after adding command, I added a new command what do I update, post-command documentation, new slash command docs.
Close a PRD that is already implemented or no longer needed