fworks-tech
- 65 skills
- 0 followers
- 13 hours ago last updated
- ▌ AWS · fworks-techManage AWS resources via the aws CLI. Use when managing S3, EC2, Lambda, or other AWS services.
- ▌ Jira · fworks-techManage Jira issues, sprints, and epics via the jira-cli. Use when viewing, creating, or updating Jira issues.
- ▌ API · fworks-techUse 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.
- ▌ Git · fworks-techUse when performing git operations — branching, rebasing, stashing, bisecting, resolving merge conflicts, or recovering lost commits. Covers advanced git workflows beyond basic add/commit/push.
- ▌ Email · fworks-techSend emails via SMTP or sendmail. Use when sending transactional emails or notifications programmatically.
- ▌ Mysql · fworks-techManage MySQL databases via the mysql CLI. Use when querying, inspecting schema, or managing MySQL databases.
- ▌ Redis · fworks-techManage Redis via the redis-cli. Use when interacting with Redis caches, queues, or key-value stores.
- ▌ Docker · fworks-techManage Docker containers and images via the docker CLI. Use when building, running, or debugging containers.
- ▌ Github · fworks-techManage GitHub repositories via the gh CLI. Use when working with issues, PRs, releases, or repository settings.
- ▌ Gitlab · fworks-techManage GitLab repositories via the glab CLI. Use when working with merge requests, issues, or CI/CD pipelines.
- ▌ Linear · fworks-techManage Linear issues and projects via the linear CLI. Use when viewing, creating, or updating Linear tasks.
- ▌ Sentry · fworks-techMonitor and debug application errors via Sentry MCP and CLI. Use when triaging production errors or managing releases.
- ▌ Redis 2 · fworks-techUse 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.
- ▌ Datadog · fworks-techMonitor infrastructure and applications via Datadog API and CLI. Use when querying metrics, logs, or managing monitors.
- ▌ Mongodb · fworks-techManage MongoDB databases via the mongosh CLI. Use when querying, inspecting, or managing MongoDB collections.
- ▌ Docker 2 · fworks-techUse 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.
- ▌ Postgres · fworks-techManage PostgreSQL databases via the psql CLI. Use when querying, inspecting schema, or managing PostgreSQL databases.
- ▌ Remember · fworks-techReviews 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 we learned", "update memory", or "capture learnings".
- ▌ Telegram · fworks-techSend messages and manage Telegram bots via the Bot API. Use when sending notifications or building chat interactions.
- ▌ The Envoy · fworks-techDetects 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. Use when onboarding a new AI provider or migrating skill formats.
- ▌ Postgres 2 · fworks-techUse 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.
- ▌ Kubernetes · fworks-techManage Kubernetes clusters via kubectl. Use when deploying, inspecting, or debugging Kubernetes resources.
- ▌ The Herald · fworks-techManages 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.
- ▌ The Oracle · fworks-techHolds 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 exploration required.
- ▌ The Scribe · fworks-techWrites commit messages, PR descriptions, and changelogs from diffs and branch history. Use whenever staging a commit, opening a PR, or preparing a release. The Scribe turns your diff into prose worth reading.
- ▌ The Tester · fworks-techDrives test-driven development, generates tests for existing code, and reviews coverage quality. Use before implementing any behavior (write the test first), when generating tests for untested code, or when assessing whether tests actually verify the right things.
- ▌ The Warden · fworks-techDetects code smell, complexity violations, architectural boundary breaches, dead code, and dependency decay in project code. Runs on every PR diff and on demand for full codebase scans. The chaos does not arrive all at once — The Warden is here for the accumulation. Use on PR diffs and codebase quality scans.
- ▌ Code Review · fworks-techDeprecated alias for the-reviewer. Do not select directly; load skills/the-reviewer/SKILL.md instead.
- ▌ The Auditor · fworks-techReviews code for security vulnerabilities, dependency risks, and access control issues. Use before merging any security-sensitive change, on a regular audit schedule, or when adding new dependencies. The Auditor assumes breach and reads code the way an attacker would.
- ▌ The Builder · fworks-techUse 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.
- ▌ The Doorman · fworks-techValidates 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.
- ▌ The Mailman · fworks-techManages message delivery, content scheduling, notification dispatch, and channel management. Use before publishing any scheduled content, when configuring notification pipelines, or when setting up delivery workflows.
- ▌ The Steward · fworks-techMonitors 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 prevent. Use at the start of any session or when context capacity tightens.
- ▌ MCP Github · fworks-techUse 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.
- ▌ The Debugger · fworks-techDiagnoses errors, traces root causes, and guides systematic recovery. Use when encountering any error, failing test, or unexpected behavior. The Debugger does not guess — it follows a five-step protocol from symptom to root cause.
- ▌ The Mediator · fworks-techListens to user prompts first, classifies intent, and hands off to the right specialist — The Strategist for deep refinement, The Steward for load/context routing, The Doorman for entry-format validation, or the executing specialist directly. Use when a request arrives and no member is immediately in charge. The Mediator is first in line.
- ▌ The Operator · fworks-techManages runtime health, deployment, incidents, rollback, and monitoring for agenthood services. Use during deployment verification or incident triage.
- ▌ The Reviewer · fworks-techConducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human.
- ▌ The Sentinel · fworks-techAudits 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. Use after creating or updating member files.
- ▌ Elasticsearch · fworks-techManage Elasticsearch clusters via the REST API. Use when querying, indexing, or managing Elasticsearch indices.
- ▌ Issue Manager · fworks-techCreates 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.
- ▌ Release Notes · fworks-techDeprecated alias for the-herald. Do not select directly; load skills/the-herald/SKILL.md instead.
- ▌ The Architect · fworks-techDrives spec-first development, task decomposition, and architecture decisions. Use before any non-trivial implementation begins. Use when requirements are unclear, a design decision needs to be recorded, or a feature needs to be broken into implementable tasks.
- ▌ The Inspector · fworks-techSolve 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 low-resolution images, multi-panel figures, or benchmark-style vision questions.
- ▌ The Librarian · fworks-techCreates 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.
- ▌ Runtime Health · fworks-techDeprecated alias for the-operator. Do not select directly; load skills/the-operator/SKILL.md instead.
- ▌ The Strategist · fworks-techTranslates ambiguous goals into structured problem statements, success criteria, and ranked priorities before the Architect starts planning. Use when requirements are vague, a feature request needs refinement, or the path from "what" to "how" is unclear. The Strategist fills the gap between "ship this feature" and "here is the spec."
- ▌ Commit Messages · fworks-techWrites conventional commit messages, PR descriptions, and changelogs from diffs and branch history. Use when staging a commit.
- ▌ Context Economy · fworks-techMonitors context window capacity, routes tasks to minimal member set, and triggers session triage. Use when managing session capacity.
- ▌ Debugging Tutor · fworks-techTeaches 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.
- ▌ Onboarding Plan · fworks-techCreates 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.
- ▌ Bug Fix Teammate · fworks-techIdentifies 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.
- ▌ Concept Explainer · fworks-techBreaks 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.
- ▌ Society Integrity · fworks-techAudits member files for internal consistency, cross-member contradictions, and structural drift. Use when validating member structure.
- ▌ Cleanup Specialist · fworks-techRemoves 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 · fworks-techAudits 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.
- ▌ Implementation Planner · fworks-techDeprecated alias for the-architect. Do not select directly; load skills/the-architect/SKILL.md instead.
- ▌ Pull Request Assistant · fworks-techGenerates comprehensive pull request descriptions and conducts structured code reviews with security, performance, testing, and documentation focus areas. Use when opening a PR or reviewing one before merge.
- ▌ Security And Hardening · fworks-techDeprecated alias for the-auditor. Do not select directly; load skills/the-auditor/SKILL.md instead.
- ▌ Institutional Knowledge · fworks-techDeprecated alias for the-oracle. Do not select directly; load skills/the-oracle/SKILL.md instead.
- ▌ Spec Driven Development · fworks-techCreates structured specifications before coding. Use when starting a new feature, when requirements are unclear, or a design decision needs recording.
- ▌ Test Driven Development · fworks-techDeprecated alias for the-tester. Do not select directly; load skills/the-tester/SKILL.md instead.
- ▌ Cross Provider Translation · fworks-techDetects AI providers, translates skill files to provider-native formats, and validates conventions. Use when onboarding new providers.
- ▌ Validation And Enforcement · fworks-techDeprecated alias for the-doorman. Do not select directly; load skills/the-doorman/SKILL.md instead.
- ▌ Debugging And Error Recovery · fworks-techDeprecated alias for the-debugger. Do not select directly; load skills/the-debugger/SKILL.md instead.