Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Remove unused translation keys from all translation files (en, he, sv, ja, es). This skill should be used when cleaning up translations, after removing features, or to reduce translation file size. Finds keys d...
Implements GitHub issues that have approved implementation plans. Use when you need to implement an issue, create a branch, write code, and submit a PR. Requires a clear implementation plan in the issue comment...
Reviews and categorizes GitHub issues by difficulty (easy/medium/hard). Use when you need to triage open issues, ask clarifying questions for incomplete issues, or write implementation plans for ready issues.
Identifies dependencies between GitHub issues and creates appropriate cross-references. Use when you need to map issue relationships, find blockers, or organize work order based on dependencies.
Prevents Git Bash path conversion issues when running Anubis commands on Windows. Use when building targets with `cargo run` or `anubis.exe` that use `//` target paths.
Defines branch naming conventions for issue work. Use when creating branches for issues, understanding work status from branches, or linking commits to issues.
Manages the Anubis Issue Tracker GitHub project board. Use when you need to organize issues by difficulty/status, move issues through workflow stages, or generate board status reports.
Prefer `cargo check` over `cargo build` when making Rust code changes. Use `cargo check` to quickly verify code compiles; only use `cargo build` when you need to run the executable.
Local-first workflow for iterative document building with GitHub gists
C# 14 and .NET 10 coding patterns, idioms, and conventions
Conventional commit format, type selection, and commit best practices
GitHub PR review operations (inline comments, pending reviews, thread resolution)
GitHub API calls for discussions and draft PRs (non-standard gh CLI patterns)
Best practices for writing AGENTS.md, agent configs, and skill files based on industry research
When writing new code, model state as sum types from the start. Apply when creating entities with distinct modes, phases, or lifecycle states.
Refactor loose state models (optional fields, parallel booleans) into strict sum types. Apply when a field's validity depends on another field's value.
Run Nx generators to scaffold code or transform existing code - for example creating libraries or apps, creating components, or anything else that is boilerplate code or automates repetitive tasks.
Guide structuring new features in Nx workspaces. Use when user asks about creating libraries, organizing code, or where to place new features.
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature,...
Facebook automation including posting with privacy settings, interactions, messaging, and navigation workflows
Utilities and patterns for detecting execution environment (CI/CD vs local, network access, available ports, timeouts). Use when you need to adapt scripts or workflows based on where the agent is running, or wh...
Enforce tight coupling between components, tests, and stories with exact naming conventions. Use when creating new components, writing tests, or ensuring test/story files exist for all user-facing components.
Comprehensive testing and verification checklist for agent-created pull requests. Use when preparing to submit a PR, verifying changes work correctly, or ensuring all evidence requirements are met. Covers Docke...
Approved libraries, bundle optimization, and security best practices for dependencies. Use when adding new packages, optimizing bundle size, or ensuring secure dependency management.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.