Menu
SkillsMP has collected 50 skills from fworks-tech/agenthood. Open a skill to review its source and details.
Showing 40 of 50 collected skills.
Audits Agenthood member files for internal consistency, cross-member contradictions, lane overlap, and structural drift against The Oracle's template. The Society cannot enforce standards it no longer understands. The Sentinel makes sure it always does.
Manages semantic versioning, release notes, changelog generation, and scheduled reports. Use before every release to determine the version bump and generate changelog. Use for daily standups and end-of-day summaries.
Creates and maintains documentation, READMEs, ADRs, and API references. Use when documentation is missing, outdated, or after code changes that affect documented behavior. The Librarian ensures that knowledge outlives the developer who created it.
Holds institutional knowledge about the Agenthood — member format, naming conventions, layer taxonomy, registration maps, and convention rationale. Ask before authoring a new member, extending the Society, or researching structure. Saves tokens. No…
Monitors context window capacity, routes tasks to the minimal required member set, optimizes member loading for provider-specific caching, and triggers session triage before capacity forces the decision. The Steward was born from the situation it exists to…
Audits member files for internal consistency, cross-member contradictions, and structural drift. Use when validating member structure.
Use when you need coding, implementation, refactoring, patching, or test work; the Builder turns concrete repo context into the smallest verified change and follows local patterns, AGENTS.md, and nearby tests.
Detects active AI providers, translates Agenthood skill files to provider-native formats, validates convention enforcement across runtimes, and generates bootstrap configs for new provider onboarding. One Society. Every runtime. No exceptions.
Detects AI providers, translates skill files to provider-native formats, and validates conventions. Use when onboarding new providers.
Holds institutional knowledge about members, conventions, and architecture. Use before authoring new members or researching patterns.
Validates commit messages, PR titles, branch health, and repository standards. Use to enforce conventions locally and in CI, run health checks, and audit repository hygiene. Nothing gets in without proper credentials.
Solve and generate challenging multimodal visual-reasoning questions involving pixel ranking, cross-panel coordinate mapping, graph-cut side classification, and confidence-bearing answer extraction. Use when the task asks for precise interpretation of…
Manages message delivery, content scheduling, notification dispatch, and cross-posting across channels. Use before publishing any scheduled content, when configuring notification pipelines, or when setting up cross-platform distribution workflows.
Manage AWS resources via the aws CLI. Use when managing S3, EC2, Lambda, or other AWS services.
Monitor infrastructure and applications via Datadog API and CLI. Use when querying metrics, logs, or managing monitors.
Manage Docker containers and images via the docker CLI. Use when building, running, or debugging containers.
Manage Elasticsearch clusters via the REST API. Use when querying, indexing, or managing Elasticsearch indices.
Send emails via SMTP or sendmail. Use when sending transactional emails or notifications programmatically.
Manage GitHub repositories via the gh CLI. Use when working with issues, PRs, releases, or repository settings.
Manage GitLab repositories via the glab CLI. Use when working with merge requests, issues, or CI/CD pipelines.
Manage Jira issues, sprints, and epics via the jira-cli. Use when viewing, creating, or updating Jira issues.
Manage Kubernetes clusters via kubectl. Use when deploying, inspecting, or debugging Kubernetes resources.
Manage Linear issues and projects via the linear CLI. Use when viewing, creating, or updating Linear tasks.
Manage MongoDB databases via the mongosh CLI. Use when querying, inspecting, or managing MongoDB collections.
Manage MySQL databases via the mysql CLI. Use when querying, inspecting schema, or managing MySQL databases.
Manage PostgreSQL databases via the psql CLI. Use when querying, inspecting schema, or managing PostgreSQL databases.
Manage Redis via the redis-cli. Use when interacting with Redis caches, queues, or key-value stores.
Monitor and debug application errors via the Sentry CLI. Use when triaging production errors or managing releases.
Send messages and manage Telegram bots via the Bot API. Use when sending notifications or building chat interactions.
Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change.
Detects code smell, complexity violations, architectural boundary breaches, and dead code. Use for codebase quality scans.
Writes conventional commit messages, PR descriptions, and changelogs from diffs and branch history. Use when staging a commit.
Monitors context window capacity, routes tasks to minimal member set, and triggers session triage. Use when managing session capacity.
Diagnoses errors, traces root causes, and guides systematic recovery. Use when encountering any error, failing test, or unexpected behavior.
Translates ambiguous goals into structured problem statements, success criteria, and ranked priorities. Use when requirements are vague.
Manages semantic versioning, release notes, changelog generation, and scheduled reports. Use before every release.
Manages runtime health, deployment, incidents, rollback, and monitoring. Use during deployment verification and incident triage.
Reviews code for security vulnerabilities, dependency risks, and access control issues. Use before merging security-sensitive changes.
Creates structured specifications before coding. Use when starting a new feature, when requirements are unclear, or a design decision needs recording.
Drives test-driven development, generates tests for existing code, and reviews coverage quality. Use before implementing any behavior.