.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

…/jamie8johnson/cqs
home/skills/jamie8johnson/cqs
jamie8johnson avatar

jamie8johnson/cqs

22 skills

View on GitHub
$npx skills add jamie8johnson/cqs
SkillInstalls
archeoComment-archaeology sweep - find work items hiding in TODO/FIXME/for-now comments and plan-doc ledgers, judge them, file issues, queue trivial fixes.—auditRun a multi-category code audit on the cqs codebase. Spawns parallel agents per batch.—before-editRun before modifying a function — impact + test-map + explain in one pass, presented as a modification checklist.—boundary-probeTrust-boundary security audit of cqs — fans out unbiddable-auditor agents across 6 categories (RT-INJ/RT-FS/RT-RES/RT-DATA/RT-RELAY/RT-EXFIL), attacker…—check-my-workRun after making changes, before committing — reviews the current git diff for impact and risk via cqs review.—cqsUnified cqs CLI dispatcher — semantic code search, call graph navigation, impact analysis, quality tools, notes, and infrastructure.—cqs-batchExecute multiple cqs queries in a single persistent session via stdin batch mode.—cqs-bootstrapOne-command setup for cqs in a new project — skills, tears infrastructure, CLAUDE.md, init, index.—cqs-planTask planning with scout data + task-type templates. Produces implementation checklists.—cqs-verifyVerify all cqs features work. Run on session start and after compaction.—docs-reviewReview project docs for staleness. Checks lib.rs, Cargo.toml, README, CONTRIBUTING, SECURITY, PRIVACY, and GitHub repo metadata.—groom-notesReview, prune, and suggest notes in notes.toml. Cleans stale notes and proposes new ones from recent changes.—idleThe idle work loop - enumerate open issues and triage rows, classify fixable vs blocked, pick by value-vs-budget, dispatch.—investigateRun before starting an implementation task — scout + gather assemble relevant files, functions, tests, and notes into a brief.—landLand a ready branch - push, PR, pinned CI watch, squash-merge, issue verification, cleanup.—migrateHandle cqs schema version upgrades — check version, attempt migration, rebuild if needed.—prCreate a pull request with WSL-safe workflow. Uses --body-file to avoid heredoc permission corruption.—recall-gateRun the retrieval recall gate with dead-gold triage and the binary A/B regression test. Required before release tags; use after any retrieval-adjacent merge.—reindexRebuild the cqs index and show before/after stats comparison.—releaseRelease a new version of cqs. Bumps version, updates changelog, runs the recall gate, publishes to crates.io, creates GitHub release.—troubleshootDiagnose common cqs issues — stale index, model download, schema mismatch, connection issues.—update-tearsUpdate PROJECT_CONTINUITY.md and notes.toml with current session state. Use proactively before context compaction or when switching tasks.—