skills/magnus919_agent-skills
1
0
Fork 0
mirror of https://github.com/magnus919/agent-skills.git synced 2026-09-11 19:47:12 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix: repair dead cross-skill routing references in methodology skills (#251)

Browse Source 
Route methodology skills to real catalog skills instead of dead role names:
- platform-engineering: docker-management -> docker-compose
- backend-engineering: technical-architect -> api-design-and-evolution,
  reviewer -> qa-methodology
- frontend-engineering: ux-designer -> product-design-and-ux,
  technical-architect -> api-design-and-evolution, writer -> neutral,
  reviewer -> qa-methodology
- security-audit-methodology: reviewer -> qa-methodology,
  debugger -> systematic-debugging
- data-engineering: UX designer -> product-design-and-ux
- technical-documentation: writer -> neutral, technical architect ->
  software-architecture-analysis, debugger -> systematic-debugging,
  reviewer -> qa-methodology
- operational-design: executive-methodology -> strategy-frameworks
- technical-documentation/references/agent-facing-docs.md: drop dead
  deployment-methodology skill_view example

Also bring modified skills' descriptions up to the quality validator's
imperative-verb + negative-boundary requirement and regenerate catalogs.

agent-council's external hermes-profiles list is retained unchanged.

Closes #234

Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
This commit is contained in:
Magnus Hedemark
2026-08-03 13:57:25 -04:00
committed by GitHub
co-authored by factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
parent dfde242608
commit 0223e2bc18
11 changed files with 60 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude-plugin/marketplace.json
+6 -6
View File
@@ -84,7 +84,7 @@
"./backend-engineering"
],
"strict": false,
"description": "Backend engineering methodology — API implementation patterns (REST, gRPC, GraphQL), service architecture (clean/hexagonal/layered), database access patterns, integration and middleware design, error handling, and service-level testing. Language and framework agnostic."
"description": "Design and implement backend services and APIs — REST, gRPC, GraphQL endpoint patterns, service architecture (clean/hexagonal/layered), database access patterns, integration and middleware design, error handling, and service-level testing. Language and framework agnostic. Do not use for frontend, data engineering, or platform infrastructure provisioning."
},
{
"name": "binary-analysis",
@@ -228,7 +228,7 @@
"./data-engineering"
],
"strict": false,
"description": "Data engineering methodology — database operations (vector, relational, graph, time-series), ETL/ELT pipeline design (dbt patterns, incremental loading), SQL analytical patterns, data quality monitoring, schema migration, and storage infrastructure management. Grounded in operational patterns for production data systems."
"description": "Design and operate data infrastructure — database operations (vector, relational, graph, time-series), ETL/ELT pipeline design (dbt patterns, incremental loading), SQL analytical patterns, data quality monitoring, schema migration, and storage infrastructure management. Do not use for statistical analysis or ML model development."
},
{
"name": "data-scientist",
@@ -336,7 +336,7 @@
"./frontend-engineering"
],
"strict": false,
"description": "Frontend engineering methodology — component architecture, state management, API integration, responsive layout, client-side performance, and frontend testing patterns. Framework agnostic, focused on web frontend implementation."
"description": "Build and maintain web frontends — component architecture, state management, API integration, responsive layout, client-side performance, and frontend testing patterns. Framework agnostic, focused on web frontend implementation. Do not use for backend service implementation, data engineering, or platform infrastructure work."
},
{
"name": "ghost-cli",
@@ -624,7 +624,7 @@
"./operational-design"
],
"strict": false,
"description": "COO methodology for process design, organizational scaling, operational metrics, compliance and audit, vendor management, and team topology. Covers value stream mapping, BPMN, bottleneck analysis, scaling from 10 to 100 to 1000 people, KPI design, balanced scorecard, SOC 2, ISO 27001, GDPR readiness, RFP processes, SLA design, vendor scorecards, team topologies, Conway's Law, and Dunbar's Number."
"description": "Design and improve operational processes and organizational scaling — process design, operational metrics, compliance and audit, vendor management, and team topology. Covers value stream mapping, BPMN, bottleneck analysis, scaling from 10 to 100 to 1000 people, KPI design, balanced scorecard, SOC 2, ISO 27001, GDPR readiness, RFP processes, SLA design, vendor scorecards, team topologies, Conway's Law, and Dunbar's Number. Do not use for engineering delivery, financial modeling, or technology evaluation."
},
{
"name": "org-design",
@@ -894,7 +894,7 @@
"./security-audit-methodology"
],
"strict": false,
"description": "Plan authorized security reviews with threat modeling, architecture and dependency audits, and vulnerability classification. Use for scoped defensive security assessment."
"description": "Plan authorized security reviews with threat modeling, architecture and dependency audits, and vulnerability classification. Use for scoped defensive security assessment. Do not use for offensive operations, unauthorized testing, or security control implementation."
},
{
"name": "seo-audit",
@@ -975,7 +975,7 @@
"./technical-documentation"
],
"strict": false,
"description": "Create and review technical documentation, including READMEs, agent-facing instructions, API references, and CLI help. Use when documentation must help someone complete real work."
"description": "Create and review technical documentation, including READMEs, agent-facing instructions, API references, and CLI help. Use when documentation must help someone complete real work. Do not use for marketing copy, brand messaging, or long-form editorial content."
},
{
"name": "technology-radar",
README.md
+4 -4
View File
@@ -42,7 +42,7 @@ An expert-level skill for building **conversational multi-agent systems** with M
### [backend-engineering](backend-engineering/SKILL.md)
Backend engineering methodology — API implementation patterns (REST, gRPC, GraphQL), service architecture (clean/hexagonal/layered), database access patterns, integration and middleware design, error handling, and service-level testing. Language and framework agnostic.
Design and implement backend services and APIs — REST, gRPC, GraphQL endpoint patterns, service architecture (clean/hexagonal/layered), database access patterns, integration and middleware design, error handling, and service-level testing. Language and framework agnostic. Do not use for frontend, data engineering, or platform infrastructure provisioning.
### [binary-analysis](binary-analysis/SKILL.md)
@@ -106,7 +106,7 @@ Act as a virtual data architect. Discover data assets, assess maturity, evaluate
### [data-engineering](data-engineering/SKILL.md)
Data engineering methodology — database operations (vector, relational, graph, time-series), ETL/ELT pipeline design (dbt patterns, incremental loading), SQL analytical patterns, data quality monitoring, schema migration, and storage infrastructure management. Grounded in operational patterns for production data systems.
Design and operate data infrastructure — database operations (vector, relational, graph, time-series), ETL/ELT pipeline design (dbt patterns, incremental loading), SQL analytical patterns, data quality monitoring, schema migration, and storage infrastructure management. Do not use for statistical analysis or ML model development.
### [data-scientist](data-scientist/SKILL.md)
@@ -158,7 +158,7 @@ Safe Forgejo API v1 CLI for issues, pull requests, repositories, file contents,
### [frontend-engineering](frontend-engineering/SKILL.md)
Frontend engineering methodology — component architecture, state management, API integration, responsive layout, client-side performance, and frontend testing patterns. Framework agnostic, focused on web frontend implementation.
Build and maintain web frontends — component architecture, state management, API integration, responsive layout, client-side performance, and frontend testing patterns. Framework agnostic, focused on web frontend implementation. Do not use for backend service implementation, data engineering, or platform infrastructure work.
### [ghost-cli](ghost-cli/SKILL.md)
@@ -293,7 +293,7 @@ Comprehensive open source contribution guidance — from reading CONTRIBUTING.md
### [operational-design](operational-design/SKILL.md)
COO methodology for process design, organizational scaling, operational metrics, compliance and audit, vendor management, and team topology. Covers value stream mapping, BPMN, bottleneck analysis, scaling from 10 to 100 to 1000 people, KPI design, balanced scorecard, SOC 2, ISO 27001, GDPR readiness, RFP processes, SLA design, vendor scorecards, team topologies, Conway's Law, and Dunbar's Number.
Design and improve operational processes and organizational scaling — process design, operational metrics, compliance and audit, vendor management, and team topology. Covers value stream mapping, BPMN, bottleneck analysis, scaling from 10 to 100 to 1000 people, KPI design, balanced scorecard, SOC 2, ISO 27001, GDPR readiness, RFP processes, SLA design, vendor scorecards, team topologies, Conway's Law, and Dunbar's Number. Do not use for engineering delivery, financial modeling, or technology evaluation.
### [org-design](org-design/SKILL.md)
backend-engineering/SKILL.md
+8 -7
View File
@@ -1,9 +1,10 @@
---
name: backend-engineering
description: Backend engineering methodology — API implementation patterns (REST,
gRPC, GraphQL), service architecture (clean/hexagonal/layered), database access
patterns, integration and middleware design, error handling, and service-level testing.
Language and framework agnostic.
description: Design and implement backend services and APIs — REST, gRPC, GraphQL
endpoint patterns, service architecture (clean/hexagonal/layered), database access
patterns, integration and middleware design, error handling, and service-level
testing. Language and framework agnostic. Do not use for frontend, data engineering,
or platform infrastructure provisioning.
license: MIT
metadata:
tags: backend, api, services, server, database, integration, middleware, query-optimization,
@@ -13,16 +14,16 @@ metadata:
# Backend Engineering Methodology
Backend engineering is the craft of building the server-side systems that power applications — APIs, services, data access, integrations, and the runtime behavior that makes the architecture real. This methodology covers the implementation patterns between architecture design (technical-architect) and quality validation (reviewer).
Backend engineering is the craft of building the server-side systems that power applications — APIs, services, data access, integrations, and the runtime behavior that makes the architecture real. This methodology covers the implementation patterns between architecture design (software-architecture-analysis) and quality validation (qa-methodology).
## The Backend Engineer's Domain
| You own | You don't own |
|---------|--------------|
| API implementation — REST/gRPC/GraphQL endpoints, request validation, response formatting, error handling, middleware chains | API contract and service boundary design — that's the technical-architect |
| API implementation — REST/gRPC/GraphQL endpoints, request validation, response formatting, error handling, middleware chains | API contract and service boundary design — that's the api-design-and-evolution |
| Service logic — business rules, workflow orchestration, state management, background job processing | Deployment pipeline and infrastructure — that's the platform-engineer |
| Database access patterns — query design, connection management, transaction boundaries, N+1 detection, pagination | Schema design and migrations — that's the data-architect / data-engineer |
| Integration code — third-party API clients, webhook handlers, message queue consumers/producers | Code review and quality gates — that's the reviewer |
| Integration code — third-party API clients, webhook handlers, message queue consumers/producers | Code review and quality gates — that's the qa-methodology |
| Observability instrumentation at the service level — structured logging, metrics, tracing hooks | Observability infrastructure — that's the SRE / platform-engineer |
| Service-level tests — unit tests for business logic, integration tests for API contracts | Test strategy and automation — that's the QA-engineer |
data-engineering/SKILL.md
+6 -6
View File
@@ -1,10 +1,10 @@
---
name: data-engineering
description: Data engineering methodology — database operations (vector, relational,
graph, time-series), ETL/ELT pipeline design (dbt patterns, incremental loading),
SQL analytical patterns, data quality monitoring, schema migration, and storage
infrastructure management. Grounded in operational patterns for production data
systems.
description: Design and operate data infrastructure — database operations (vector,
relational, graph, time-series), ETL/ELT pipeline design (dbt patterns, incremental
loading), SQL analytical patterns, data quality monitoring, schema migration, and
storage infrastructure management. Do not use for statistical analysis or ML model
development.
license: MIT
metadata:
tags: data-engineering, etl, dbt, sql, database, graph-db, time-series, vector-db,
@@ -25,7 +25,7 @@ Data engineering is the operational backbone of data-driven systems. This method
| Analytical SQL — window functions, CTEs, query optimization, execution plan analysis, star schema queries | Training infrastructure and model deployment — that's the ML engineer |
| Graph database operations — Neo4j data modeling, Cypher queries, graph algorithms, import/export | Application-level data access patterns — that's the developer |
| Time-series database operations — InfluxDB schema design, downsampling, retention policies, Telegraf | Infrastructure provisioning — that's the platform engineer |
| Data quality monitoring — integrity checks, deduplication, anomaly detection, freshness validation | Visual dashboard design — that's the analyst or UX designer |
| Data quality monitoring — integrity checks, deduplication, anomaly detection, freshness validation | Visual dashboard design — that's the analyst / product-design-and-ux |
| Storage infrastructure — capacity planning, performance tuning, archival strategies |
## Reference Files
frontend-engineering/SKILL.md
+9 -7
View File
@@ -1,8 +1,10 @@
---
name: frontend-engineering
description: Frontend engineering methodology — component architecture, state management,
description: Build and maintain web frontends — component architecture, state management,
API integration, responsive layout, client-side performance, and frontend testing
patterns. Framework agnostic, focused on web frontend implementation.
patterns. Framework agnostic, focused on web frontend implementation. Do not use
for backend service implementation, data engineering, or platform infrastructure
work.
license: MIT
metadata:
tags: frontend, web, ui, components, state-management, performance, javascript,
@@ -12,18 +14,18 @@ metadata:
# Frontend Engineering Methodology
Frontend engineering is the craft of building the user-facing layer of applications — components, state management, API integration, responsive layout, and client-side performance. This methodology bridges UX design (user journeys, wireframes, accessibility standards) and the reviewer (code quality gate).
Frontend engineering is the craft of building the user-facing layer of applications — components, state management, API integration, responsive layout, and client-side performance. This methodology bridges UX design (user journeys, wireframes, accessibility standards) and quality validation (qa-methodology).
## The Frontend Engineer's Domain
| You own | You don't own |
|---------|--------------|
| Component implementation — UI component composition, props/state interfaces, rendering patterns, lifecycle | User journeys, wireframes, accessibility standards, interaction design — that's the ux-designer |
| State management — client-side state architecture, data fetching patterns, caching, optimistic updates | API contract design — that's the technical-architect |
| Component implementation — UI component composition, props/state interfaces, rendering patterns, lifecycle | User journeys, wireframes, accessibility standards, interaction design — that's the product-design-and-ux |
| State management — client-side state architecture, data fetching patterns, caching, optimistic updates | API contract design — that's the api-design-and-evolution |
| API integration — frontend-to-backend data flow, auth flows (OAuth, JWT), real-time updates | Test strategy and automation — that's the QA-engineer |
| Responsive design implementation — layout systems, breakpoints, cross-device testing | Visual identity and brand guidelines — that's the brand-designer |
| Client-side performance — bundle optimization, lazy loading, Core Web Vitals, render optimization | Editorial content and copy — that's the writer |
| Frontend testing — component tests, integration tests, visual regression, accessibility tests | Code review and quality gates — that's the reviewer |
| Client-side performance — bundle optimization, lazy loading, Core Web Vitals, render optimization | Editorial content and copy — owned by the content and marketing team, outside this skill's scope |
| Frontend testing — component tests, integration tests, visual regression, accessibility tests | Code review and quality gates — that's the qa-methodology |
| Build tooling — bundler config, TypeScript config, linting, formatting, dev environment | CI/CD pipeline infrastructure — that's the platform-engineer |
## Reference Files
llms.txt
+6 -6
View File
@@ -10,7 +10,7 @@
- [api-design-and-evolution](api-design-and-evolution/SKILL.md): Design, document, review, and evolve consumer-facing APIs and event interfaces. Use when choosing REST/HTTP, GraphQL, RPC, events, webhooks, or streaming; writing OpenAPI or AsyncAPI contracts; defining schemas, pagination, mutations, errors, idempotency, or API compatibility; or planning API versioning, deprecation, and migration. Use secure-software-engineering for a full security lifecycle, ADR authoring for durable architecture decisions, and spec-driven-development for a delivery specification and implementation gates.
- [artifact-pyramids](artifact-pyramids/SKILL.md): Organize durable agent research outputs as summaries, analysis, and evidence dossiers. Use when producing multi-layer research artifacts or coordinating research handoffs.
- [autogen](autogen/SKILL.md): Expert skill for conversational multi-agent AI with Microsoft AutoGen. AssistantAgent, UserProxyAgent, GroupChat, code execution, nested chats, cancellation tokens, tool integration, and MCP support. Use when building conversation-driven multi-agent systems or comparing agent frameworks.
- [backend-engineering](backend-engineering/SKILL.md): Backend engineering methodology — API implementation patterns (REST, gRPC, GraphQL), service architecture (clean/hexagonal/layered), database access patterns, integration and middleware design, error handling, and service-level testing. Language and framework agnostic.
- [backend-engineering](backend-engineering/SKILL.md): Design and implement backend services and APIs — REST, gRPC, GraphQL endpoint patterns, service architecture (clean/hexagonal/layered), database access patterns, integration and middleware design, error handling, and service-level testing. Language and framework agnostic. Do not use for frontend, data engineering, or platform infrastructure provisioning.
- [binary-analysis](binary-analysis/SKILL.md): Analyze unknown binary files through a deterministic CLI that wraps Ghidra's static-analysis engine. Use when you need to inspect a PE, ELF, or Mach-O file — triage suspicious binaries, map imported APIs, decompile functions, trace call paths, or produce structured evidence reports. Do not use for runtime analysis (debugging, dynamic tracing, sandbox execution), for modifying or patching binaries, or for binaries you already know everything about. The skill owns planning, hypothesis formation, and evidence synthesis; the CLI owns all deterministic operations.
- [brand-designer](brand-designer/SKILL.md): Create comprehensive brand identity documentation for any brand. Guides you through documenting strategy, visual identity (logo, color, typography, imagery), voice and tone, application guidelines, governance, and asset inventory. Produces markdown specs, compiled brand books, and brand-compliant images via reference-image-aware generation. Use when you need to capture a brand's identity in structured, durable form — for vault storage, agency handoff, or press kit distribution.
- [c4-diagramming](c4-diagramming/SKILL.md): Create C4 software-architecture diagrams using Mermaid or Structurizr. Use when teams need clear system context, container, component, or code-level views.
@@ -26,7 +26,7 @@
- [cyberpunk](cyberpunk/SKILL.md): Create or analyze settings, scenes, world operations, and image direction in the literary cyberpunk mode of William Gibson's Sprawl fiction: dense, accreted urban systems; uneven high technology; corporate power; mediated culture; and human-scale survival inside global networks. Use for Gibson-informed creative work, setting design, or visual briefs, not for generic neon cyberpunk, faithful continuation of named canon, or imitation of Gibson's prose.
- [daily-life-discovery](daily-life-discovery/SKILL.md): Guide a consent-based conversation that helps a person discover how an AI agent could improve their day-to-day life: routines, friction, attention, decisions, relationships, learning, and small experiments. Use when someone asks for a daily check-in, wants the agent to learn how they work, says "grill me," wants a conversational journal, or asks what an AI could help with. Do not use for therapy, diagnosis, crisis support, covert monitoring, or product requirements interviews.
- [data-architect](data-architect/SKILL.md): A virtual data architect for teams who don't have one. If your data pipelines are growing faster than your team, nobody agrees on what 'customer' means, your cloud bill is climbing without clear reason, or you're about to choose a data platform and need someone who's seen this before — load this skill. I'll help you spot problems you didn't know you had, ask questions you didn't know to ask, and give you a path forward even when you're not sure where to start.
- [data-engineering](data-engineering/SKILL.md): Data engineering methodology — database operations (vector, relational, graph, time-series), ETL/ELT pipeline design (dbt patterns, incremental loading), SQL analytical patterns, data quality monitoring, schema migration, and storage infrastructure management. Grounded in operational patterns for production data systems.
- [data-engineering](data-engineering/SKILL.md): Design and operate data infrastructure — database operations (vector, relational, graph, time-series), ETL/ELT pipeline design (dbt patterns, incremental loading), SQL analytical patterns, data quality monitoring, schema migration, and storage infrastructure management. Do not use for statistical analysis or ML model development.
- [data-scientist](data-scientist/SKILL.md): PhD-level expertise in data science, statistics, and machine learning. Use when the task requires rigorous statistical analysis, experimental design, causal inference, advanced modeling, research methodology, or data science project leadership. Load when the user asks about statistical methods, experimental design, model selection, A/B testing, hypothesis testing, power analysis, regression, causality, Bayesian analysis, or research methodology.
- [de-spin](de-spin/SKILL.md): Use when someone asks what is true, false, misleading, unsupported, unknown, or genuinely complicated in a persuasive message, article, pitch, advertisement, policy claim, or viral post. Analyze propaganda, spin, selective framing, urgency, social proof, deceptive marketing, and AI-generated persuasion by tracing claims to evidence and separating literal truth from implied conclusions. Do not use to read deception from demeanor, adjudicate intent, or replace broad domain research.
- [docker-compose](docker-compose/SKILL.md): Use Docker Compose to define, run, debug, and harden multi-container applications. Load for compose.yaml design, networking, volumes, secrets, profiles, overrides, watch mode, lifecycle operations, or troubleshooting.
@@ -38,7 +38,7 @@
- [flaresolverr](flaresolverr/SKILL.md): Use the minimal FlareSolverr wrapper for a one-off health check or browser-backed GET/POST when ordinary retrieval is blocked by Cloudflare or DDoS-GUARD. Choose flaresolverr-cli instead for named session lifecycle, cookie-only returns, dry-run planning, or the full operational command surface.
- [flaresolverr-cli](flaresolverr-cli/SKILL.md): Use a small FlareSolverr JSON CLI for browser-backed GET and POST requests, readiness checks, and session lifecycle management when a site requires Cloudflare or DDoS-GUARD challenge handling.
- [forgejo-cli](forgejo-cli/SKILL.md): Use when managing a Forgejo or Gitea server from the terminal: issues, pull requests, repositories, file contents, labels, milestones, releases, webhooks, user settings, or any /api/v1 endpoint through a safe generic API command.
- [frontend-engineering](frontend-engineering/SKILL.md): Frontend engineering methodology — component architecture, state management, API integration, responsive layout, client-side performance, and frontend testing patterns. Framework agnostic, focused on web frontend implementation.
- [frontend-engineering](frontend-engineering/SKILL.md): Build and maintain web frontends — component architecture, state management, API integration, responsive layout, client-side performance, and frontend testing patterns. Framework agnostic, focused on web frontend implementation. Do not use for backend service implementation, data engineering, or platform infrastructure work.
- [ghost-cli](ghost-cli/SKILL.md): Manage Ghost CMS content from the terminal — create and list posts, pages, and tags, and fetch site info via the Ghost Admin API (v5/v6). Use when the user asks about ghost, cms, blog, blogging, posts, pages, tags, publishing, or site configuration.
- [github-runner](github-runner/SKILL.md): Deploy, manage, and troubleshoot self-hosted GitHub Actions runners. Covers systemd service, Docker containers, Kubernetes (Actions Runner Controller), and the Scale Set Client. Use when setting up a CI runner, debugging registration failures, designing autoscaling, or hardening runner security.
- [go-to-market](go-to-market/SKILL.md): CMO methodology — positioning and messaging frameworks (April Dunford's positioning, message hierarchy), customer acquisition strategy (paid, organic, PLG, SLG), brand architecture (brand house vs house of brands), growth modeling (CAC/LTV by channel, cohort analysis), market entry strategy (beachhead, land-and-expand), competitive response (pricing wars, feature races, brand defense).
@@ -70,7 +70,7 @@
- [open-knowledge-format](open-knowledge-format/SKILL.md): Google's Open Knowledge Format (OKF) v0.1 — an open, vendor-neutral spec for representing knowledge as markdown files with YAML frontmatter, designed for AI agent consumption. Use when the user mentions OKF, Open Knowledge Format, Google's knowledge format, LLM wiki bundles, agent knowledge packs, creating OKF bundles, validating OKF documents, or converting knowledge into the OKF standard.
- [openlibrary-cli](openlibrary-cli/SKILL.md): Search books, authors, and works on Open Library from the terminal. Look up books by ISBN, search titles and authors, and fetch detailed work/author records via the public Open Library API. No API key required.
- [opensource-contributions](opensource-contributions/SKILL.md): Make good open source contributions — check CONTRIBUTING.md first, follow project norms, be a good citizen. Covers bug reports, feature requests, and pull requests with a defensible default posture when the project hasn't documented expectations.
- [operational-design](operational-design/SKILL.md): COO methodology for process design, organizational scaling, operational metrics, compliance and audit, vendor management, and team topology. Covers value stream mapping, BPMN, bottleneck analysis, scaling from 10 to 100 to 1000 people, KPI design, balanced scorecard, SOC 2, ISO 27001, GDPR readiness, RFP processes, SLA design, vendor scorecards, team topologies, Conway's Law, and Dunbar's Number.
- [operational-design](operational-design/SKILL.md): Design and improve operational processes and organizational scaling — process design, operational metrics, compliance and audit, vendor management, and team topology. Covers value stream mapping, BPMN, bottleneck analysis, scaling from 10 to 100 to 1000 people, KPI design, balanced scorecard, SOC 2, ISO 27001, GDPR readiness, RFP processes, SLA design, vendor scorecards, team topologies, Conway's Law, and Dunbar's Number. Do not use for engineering delivery, financial modeling, or technology evaluation.
- [org-design](org-design/SKILL.md): CHRO methodology — organizational design (team topologies, span of control, reporting structures), talent strategy (make-vs-buy, skill taxonomies, succession planning), compensation frameworks (market benchmarking, equity design, leveling), culture architecture (values codification, rituals, psychological safety), organizational health metrics (eNPS, retention risk, engagement surveys), DEI strategy (inclusive design, equitable systems, belonging).
- [pace-plan](pace-plan/SKILL.md): Build, coordinate, operate, troubleshoot, exercise, and improve an authorized Primary, Alternate, Contingency, and Emergency communications plan. Use for resilient emergency-communications paths and their ownership, triggers, check-ins, tests, and corrective actions. Do not use for generic incident status messaging, frequency or channel planning, radio programming, or unauthorized transmission and activation.
- [peertube](peertube/SKILL.md): Browse PeerTube federated video from the terminal: view videos and channels, search across instances, check server stats, and manage your account. Uses OAuth2 authentication with token persistence. Use when the user mentions PeerTube, federated video, decentralized video platforms, or browsing/uploading to a PeerTube instance.
@@ -100,7 +100,7 @@
- [resilience-and-recovery](resilience-and-recovery/SKILL.md): Design, exercise, and evidence graceful degradation, disaster recovery, and restoration behavior across systems and dependencies. Covers failure-mode analysis, RTO/RPO decision records, restore testing, game days, failover drills, data integrity verification, and recovery communication. Do not use for live incident command or incident response; route to site-reliability-engineering for those. Do not use for infrastructure implementation details; route to platform-engineering.
- [restic](restic/SKILL.md): Install, configure, operate, secure, automate, tune, troubleshoot, and recover restic backups across local, SFTP, S3-compatible, cloud, and REST backends. Use when creating or managing a restic repository, designing backup or retention policy, validating restores, handling repository health or locks, moving repositories, or building safe scheduled backup jobs. Do not use for a generic file-copy task that does not need encrypted, deduplicated snapshots.
- [secure-software-engineering](secure-software-engineering/SKILL.md): Use when designing or implementing software securely: define security requirements, threat-model a feature, choose secure defaults, design authentication and authorization, handle untrusted data and secrets, evaluate dependencies, or review security-sensitive changes. Use for prevention during requirements, design, implementation, and review; not for post-build security assessments or scanning an existing codebase.
- [security-audit-methodology](security-audit-methodology/SKILL.md): Plan authorized security reviews with threat modeling, architecture and dependency audits, and vulnerability classification. Use for scoped defensive security assessment.
- [security-audit-methodology](security-audit-methodology/SKILL.md): Plan authorized security reviews with threat modeling, architecture and dependency audits, and vulnerability classification. Use for scoped defensive security assessment. Do not use for offensive operations, unauthorized testing, or security control implementation.
- [seo-audit](seo-audit/SKILL.md): Audit websites and pages for technical SEO, on-page SEO, schema markup, content discoverability, and answer-engine readiness. Use when prioritizing search visibility improvements.
- [site-reliability-engineering](site-reliability-engineering/SKILL.md): Design, operate, and improve reliable production systems with SLOs, incident command, observability, error budgets, and operational practices.
- [software-architecture-analysis](software-architecture-analysis/SKILL.md): Reverse-engineer a software codebase to understand architecture, data flow, privacy posture, and feature surface — then produce a clean-room design document, PRD, or migration plan that re-imagines the system under new constraints (local-first, privacy-first, self-hosted). Use when you need to understand how a system works from its source code or produce a specification without copying implementation details.
@@ -109,7 +109,7 @@
- [supabase](supabase/SKILL.md): Use this skill when developing applications with Supabase, running the Supabase CLI, designing migrations and RLS policies, testing database behavior, generating client types, deploying the official self-hosted Docker stack, or administering its Postgres, Auth, Storage, Realtime, Functions, API gateway, backups, upgrades, and security. Use it for managed and self-hosted projects. Do not use it for generic PostgreSQL work with no Supabase services or conventions.
- [systematic-debugging](systematic-debugging/SKILL.md): 4-phase root cause debugging protocol: understand bugs before fixing. Use for ANY technical issue — test failures, production bugs, unexpected behavior, performance problems, build failures, or integration issues. ESPECIALLY when under time pressure, when "one quick fix" seems obvious, or when previous fix attempts have failed.
- [tailscale](bundles/tailscale/SKILL.md): Self-hosted Tailscale/Headscale ecosystem: deploy and manage a Headscale control server, configure tailscale clients, manage ACL policies, node lifecycle, subnet routing, DERP relays, and backup/migration. Use when the user mentions Tailscale, Headscale, tailnet, mesh VPN, WireGuard mesh, or self-hosted VPN infrastructure.
- [technical-documentation](technical-documentation/SKILL.md): Create and review technical documentation, including READMEs, agent-facing instructions, API references, and CLI help. Use when documentation must help someone complete real work.
- [technical-documentation](technical-documentation/SKILL.md): Create and review technical documentation, including READMEs, agent-facing instructions, API references, and CLI help. Use when documentation must help someone complete real work. Do not use for marketing copy, brand messaging, or long-form editorial content.
- [technology-radar](technology-radar/SKILL.md): Build and maintain technology radars for adoption, trial, assessment, and hold decisions. Use when governing technology choices, build-versus-buy decisions, or engineering portfolio risk.
- [tempest-cli](tempest-cli/SKILL.md): Query hyper-local weather from a WeatherFlow Tempest station: current conditions, 7-day forecast, historical observations, and real-time UDP broadcasts. Use when the user asks about the weather, temperature, rain, wind, humidity, forecast, or wants conditions from their own station rather than a generic weather service.
- [three](three/SKILL.md): Build browser-based Three.js and WebGL scenes, animations, and interactive 3D visualizations with a small vanilla JavaScript starting point.
operational-design/SKILL.md
+9 -8
View File
@@ -1,10 +1,12 @@
---
name: operational-design
description: COO methodology for process design, organizational scaling, operational
metrics, compliance and audit, vendor management, and team topology. Covers value
stream mapping, BPMN, bottleneck analysis, scaling from 10 to 100 to 1000 people,
KPI design, balanced scorecard, SOC 2, ISO 27001, GDPR readiness, RFP processes,
SLA design, vendor scorecards, team topologies, Conway's Law, and Dunbar's Number.
description: Design and improve operational processes and organizational scaling — process
design, operational metrics, compliance and audit, vendor management, and team
topology. Covers value stream mapping, BPMN, bottleneck analysis, scaling from 10
to 100 to 1000 people, KPI design, balanced scorecard, SOC 2, ISO 27001, GDPR readiness,
RFP processes, SLA design, vendor scorecards, team topologies, Conway's Law, and
Dunbar's Number. Do not use for engineering delivery, financial modeling, or technology
evaluation.
license: MIT
metadata:
tags: coo, operations, process-design, scaling, compliance, vendor-management, team-topologies
@@ -44,7 +46,7 @@ Load this skill when the task involves:
```
skill_view('operational-design') # This — methodology index
skill_view('executive-methodology') # Shared decision frameworks
skill_view('strategy-frameworks') # Shared decision frameworks
skill_view('artifact-pyramids') # Output contract
skill_view('operational-design', file_path='references/process-design.md')
skill_view('operational-design', file_path='references/scaling-frameworks.md')
@@ -74,8 +76,7 @@ skill_view('operational-design', file_path='references/vendor-management.md')
## Related Skills
- `executive-methodology` — shared decision frameworks and governance
- `strategy-frameworks` — CEO-side strategic direction and competitive analysis
- `strategy-frameworks` — CEO-side strategic direction, competitive analysis, and shared decision frameworks
- `technology-radar` — CTO-side technology evaluation and architecture governance
- `financial-modeling` — CFO-side unit economics and SaaS metrics
- `artifact-pyramids` — output contract specification
platform-engineering/SKILL.md
+2 -2
View File
@@ -39,7 +39,7 @@ Use [release-engineering](../release-engineering/SKILL.md) to define release pro
```
skill_view('platform-engineering') # This — methodology index
skill_view('artifact-pyramids') # Output contract
skill_view('docker-management') # Container lifecycle (if needed)
skill_view('docker-compose') # Container lifecycle and Compose (if needed)
skill_view('traefik') # Reverse proxy (if needed)
skill_view('tailscale') # Mesh networking (if needed)
skill_view('implementation-planning') # Work breakdown (if needed)
@@ -86,7 +86,7 @@ The profile using this skill produces artifact pyramids. The response to any cal
## Related Skills
- `artifact-pyramids` — output contract specification
- `docker-management` — container lifecycle and Compose
- `docker-compose` — container lifecycle and multi-container Compose orchestration
- `traefik` — reverse proxy and ingress configuration
- `tailscale` — mesh networking and ACL policies
- `implementation-planning` — work breakdown and dependency ordering
security-audit-methodology/SKILL.md
+3 -3
View File
@@ -1,6 +1,6 @@
---
name: security-audit-methodology
description: Plan authorized security reviews with threat modeling, architecture and dependency audits, and vulnerability classification. Use for scoped defensive security assessment.
description: Plan authorized security reviews with threat modeling, architecture and dependency audits, and vulnerability classification. Use for scoped defensive security assessment. Do not use for offensive operations, unauthorized testing, or security control implementation.
license: MIT
compatibility: Authorization for the target system is required. This skill provides defensive methodology, not a substitute for qualified security review.
metadata:
@@ -21,8 +21,8 @@ Security is not a checklist — it's a posture. This methodology covers systemat
| You own | You don't own |
|---------|--------------|
| Threat modeling — STRIDE, attack trees, trust boundaries | General code review — that's the reviewer |
| Vulnerability assessment — classification, severity, reproduction | Performance analysis — that's the debugger |
| Threat modeling — STRIDE, attack trees, trust boundaries | General code review — that's the qa-methodology |
| Vulnerability assessment — classification, severity, reproduction | Performance analysis — that's the systematic-debugging |
| Security architecture review — authn/authz, data flow, secrets management | Operational reliability — that's SRE |
| Dependency analysis — supply chain, known vulnerabilities, license risk | Compliance certification — that's legal |
| Security testing guidance — fuzzing, SAST/DAST integration | Incident response execution — that's SRE/on-call |
technical-documentation/SKILL.md
+5 -5
View File
@@ -1,6 +1,6 @@
---
name: technical-documentation
description: Create and review technical documentation, including READMEs, agent-facing instructions, API references, and CLI help. Use when documentation must help someone complete real work.
description: Create and review technical documentation, including READMEs, agent-facing instructions, API references, and CLI help. Use when documentation must help someone complete real work. Do not use for marketing copy, brand messaging, or long-form editorial content.
license: MIT
compatibility: No runtime dependency.
metadata:
@@ -17,12 +17,12 @@ Technical documentation is the interface between a tool and its user. This metho
| You own | You don't own |
|---------|--------------|
| API documentation — endpoint references, parameters, examples | Editorial and long-form narrative content — that's the writer |
| API documentation — endpoint references, parameters, examples | Editorial and long-form narrative content — owned by the editorial function, outside this skill's scope |
| README authorship — project overview, quickstart, configuration | Brand messaging and marketing copy — that's the brand designer |
| CLI documentation — help text, usage patterns, exit codes | Code architecture decisions — those belong to the technical architect |
| CLI documentation — help text, usage patterns, exit codes | Code architecture decisions — that's the software-architecture-analysis |
| Agent-facing docs — AGENTS.md, skill documentation | Project roadmap and product vision — that's the product manager |
| Reference documentation — config files, troubleshooting, architecture | Performance optimization guidance — that's the debugger/SRE |
| Documentation site structure — IA, cross-referencing, search | Code quality and standards — that's the reviewer/QA engineer |
| Reference documentation — config files, troubleshooting, architecture | Performance optimization guidance — that's the systematic-debugging / SRE |
| Documentation site structure — IA, cross-referencing, search | Code quality and standards — that's the qa-methodology / QA engineer |
## Reference Files
technical-documentation/references/agent-facing-docs.md
+2 -6
View File
@@ -19,12 +19,8 @@ Agent-facing docs have different requirements than human-facing docs. Agents rea
## Loading Order
Specify which skills to load and in what order. Skills should be loaded explicitly,
not assumed.
\`\`\`python
skill_view('artifact-pyramids') # 1. Output format
skill_view('deployment-methodology') # 2. Methodology
\`\`\`
not assumed. For example: load `artifact-pyramids` for the output format, then
`platform-engineering` (or `release-engineering`) for the deployment methodology.
## Output Contract