.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/alexandrbasis/claudops
home/skills/alexandrbasis/claudops
alexandrbasis avatar

alexandrbasis/claudops

40 skills

View on GitHub
$npx skills add alexandrbasis/claudops
SkillInstalls
analyzeCross-artifact consistency check between spec documents and tech decomposition.—antigravity-cliRun Google Antigravity CLI (agy) for web-grounded research, cross-AI review, or validation.—architecture-languageCanonical architectural vocabulary — module, interface, seam, adapter, depth, leverage, locality.—blueprintTurn a one-line objective into a multi-session implementation plan with cold-start briefs.—brainstormCollaborative brainstorming session on any topic — project-related or general.—cc-linearExecute Linear operations via direct GraphQL API — create issues, update status/priority/title, add comments, search tasks, manage labels, assign work, and…—code-analysisDeep code analysis with metrics, patterns, and recommendations.—codex-clicoding-conventionsInternal reference skill — coding standards and patterns for developer agents. Not user-invocable.—ctUse when a feature/scoped task is clear enough for technical planning — produces an implementation-ready technical decomposition before coding.—cursor-cliRun Cursor CLI (Composer 2, a Kimi-K2.5 lineage) for one-shot cross-AI code review when a non-OpenAI/non-Anthropic perspective is specifically wanted.—dbgDebug mode with runtime evidence and instrumentation. Use when asked to 'debug this', 'find the bug', 'troubleshoot', 'why is this broken', 'investigate…—deep-researchIn-depth research on technical topics using web search, documentation, and codebase analysis.—design-explorationExplore codebase and design approaches before implementation. Use when asked 'explore the design', 'how would this fit', 'design exploration', 'what patterns…—dev-serverStart any project's dev server and monitor it for errors in real-time.—fciFix CI pipeline failures blocking PR merge. Use when CI checks fail, 'pipeline broken', 'build failing', 'fix CI', or 'checks not passing'.—finisherClose out work by committing local changes, pushing, waiting for green CI, and merging the PR.—git-guardrailsInspect, install, customize, or troubleshoot the harness-level git safety hook that blocks dangerous git operations (push, branch -D, checkout .) before they…—grill-meUse when a plan, design, or discovery document needs stress-testing for hidden assumptions, scope gaps, unresolved branches, or ambiguous wording; also when…—improve-codebase-architectureFind deepening opportunities in a codebase — refactors that turn shallow modules into deep ones for better testability and AI-navigability.—nfRuns an in-depth feature-discovery interview that explores, challenges, and documents a new feature before planning.—parallelizationParallelize implementation across isolated git worktrees. Use when /si identifies parallelizable work, the user says 'run in parallel', 'implement…—phPrepare session handoff for continuation in a new conversation.—prcReview and address code review comments on PR. Use when asked to 'address review comments', 'fix PR feedback', 'handle review comments', 'respond to PR…—productCreate JTBD or PRD product documentation through an interactive interview process.—qaInteractive QA session where the user reports bugs conversationally and the agent files them as tracker issues (GitHub or Linear) one by one or as a…—review-conventionsInternal reference skill — shared conventions for all code review agents. Not user-invocable.—ripReview implementation plan for business value alignment. Use when asked to 'review my plan', 'walk through implementation', 'check plan against PRD', 'review…—sbsInteractive teaching guide for learning while working. Use when asked to 'teach me', 'walk me through', 'explain step by step', 'guide me through', 'show me…—setupConfigure workflow for your codebase. Run after cloning .claude/ into your repo.—siImplements a feature from a technical decomposition using TDD, keeping the task document updated and handing off cleanly to review.—si-quickUse when handling a small, untracked change with clear scope or a bugfix with a known root cause, and there is no tech-decomposition or task directory to…—srUse when asked to review code before merge or review a PR, branch, commit range, task path, or current working tree.—tddTest-driven development with red-green-refactor loop using vertical slices.—triage-issueInvestigate a reported bug, find its root cause, and file a tracker issue (GitHub or Linear) with a TDD-based fix plan.—ubiquitous-languageExtract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms.—update-docsUpdate documentation and generate changelog after task implementation.—update-setupPull upstream workflow changes from claudops into a local .claude/ folder.—vpCreate interactive visual prototype playground for user approval before technical decomposition.—zoom-outStep up one layer of abstraction and produce a map of the relevant modules and their callers — used when you (or the agent) are stuck in one file and losing…—