fworks-tech/agenthood - Page 2

linear

Manage Linear issues and projects via the linear CLI. Use when viewing, creating, or updating Linear tasks.

mongodb

Manage MongoDB databases via the mongosh CLI. Use when querying, inspecting, or managing MongoDB collections.

mysql

Manage MySQL databases via the mysql CLI. Use when querying, inspecting schema, or managing MySQL databases.

postgres

Manage PostgreSQL databases via the psql CLI. Use when querying, inspecting schema, or managing PostgreSQL databases.

redis

Manage Redis via the redis-cli. Use when interacting with Redis caches, queues, or key-value stores.

sentry

Monitor and debug application errors via Sentry MCP and CLI. Use when triaging production errors or managing releases.

telegram

Send messages and manage Telegram bots via the Bot API. Use when sending notifications or building chat interactions.

mcp-github

Use when reviewing PRs, checking CI status, or interacting with GitHub via MCP. Requires the GitHub MCP server to be configured in opencode.json or .agenthood/config.json.

api

Use when designing, building, or testing REST APIs — endpoint design, authentication, error handling, pagination, versioning, and OpenAPI documentation. Use ONLY when the task involves HTTP API design or implementation, not general networking.

docker

Use when building, running, or debugging Docker containers — Dockerfile creation, compose configurations, image optimization, volume management, and container networking. Use ONLY when the task involves Docker specifically, not general deployment.

git

Use when performing git operations — branching, rebasing, stashing, bisecting, resolving merge conflicts, or recovering lost commits. Covers advanced git workflows beyond basic add/commit/push.

postgres

Use when querying, managing, or debugging PostgreSQL databases — schema design, query optimization, migrations, indexing, and connection pooling. Use ONLY when the task involves PostgreSQL specifically, not general SQL.

redis

Use when interacting with Redis — caching strategies, pub/sub, rate limiting, session storage, queue management, and debugging key expiration. Use ONLY when the task involves Redis specifically, not general caching.

debugging-and-error-recovery

Deprecated alias for the-debugger. Do not select directly; load skills/the-debugger/SKILL.md instead.

remember

Reviews conversation history and captures valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says "remember this", "save what…

bug-fix-teammate

Identifies critical bugs in a codebase and implements targeted fixes with working code — root cause, minimal change, regression tests. Use when a bug needs to be fixed, not just diagnosed.

cleanup-specialist

Removes dead code, eliminates duplication, refactors messy patterns, and applies consistent formatting across code and documentation — safely, with tests before and after. Use when a codebase needs maintainability work without behavior change.

accessibility-auditor

Audits web interfaces for WCAG compliance — semantic HTML, ARIA, keyboard navigation, color contrast, screen reader compatibility, and accessible forms. Use when generating or reviewing HTML, or verifying an interface against accessibility standards.

debugging-tutor

Teaches systematic debugging methodology — reproduction, isolation, hypothesis formation, and independent problem-solving — rather than handing out quick fixes. Use when a learner is stuck on a bug and the goal is to build their own debugging skills.

concept-explainer

Breaks down complex technical concepts in beginner-friendly ways with analogies, practical examples, and understanding checks. Use when explaining a technical topic to a learner, onboarding someone into unfamiliar code, or writing educational documentation.

issue-manager

Creates well-structured, actionable GitHub issues and manages issue-driven work with clear titles, reproduction steps, and measurable success criteria. Use when filing bug reports, proposing features, or triaging an existing issue queue.

onboarding-plan

Creates personalized, phased onboarding plans for new team members — environment setup, codebase discovery, first contributions, and early wins. Use when a new developer joins the team and needs a structured path from first day to first contribution.

society-integrity

Audits member files for internal consistency, cross-member contradictions, and structural drift. Use when validating member structure.

cross-provider-translation

Detects AI providers, translates skill files to provider-native formats, and validates conventions. Use when onboarding new providers.

goal-refinement

Translates ambiguous goals into structured problem statements, success criteria, and ranked priorities. Use when requirements are vague.

spec-driven-development

Creates structured specifications before coding. Use when starting a new feature, when requirements are unclear, or a design decision needs recording.