@monoes/monomindcli 2.16.2 → 2.16.4

package/org-skills/energy-procurement/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: energy-procurement
-description: "Codified expertise for electricity and gas procurement, tariff optimization, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers. Includes market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks."
-tags: ["operations","finance"]
+description: "Use when buying electricity or gas for multiple facilities: supply RFPs, tariff and demand charge optimization, renewable PPA evaluation and hedging."
+tags: ["operations","finance","supply-chain"]
 tools: []
 license: Apache-2.0
 source: https://github.com/affaan-m/ECC

package/org-skills/error-handling/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: error-handling
-description: "Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages. Use when designing error types, retries, circuit breakers, or user-facing failure messages in TypeScript, Python, or Go."
-tags: ["engineering","backend"]
+description: "Use when designing error types, retries, circuit breakers, error boundaries or user-facing error messages in TypeScript, Python or Go services."
+tags: ["engineering","backend","typescript","python","go"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/event-marketing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: event-marketing
-description: "When the user wants to plan, run, sponsor, speak at, or get pipeline from events — webinars, conferences, trade shows, meetups, dinners, workshops, virtual summits, or user conferences."
-tags: ["marketing","sales"]
+description: "Use when planning, hosting, sponsoring, speaking at or attending events for pipeline: webinars, conferences, trade shows, meetups, dinners and user conferences. Covers event selection, before-and-after arcs and follow-up."
+tags: ["marketing","sales","growth"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/evidence-collector/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: evidence-collector
-description: "Evidence Collector role best practices. Gathers and verifies visual/factual proof that a claimed implementation actually works — the antidote to \"it should work\" reports that were never actually checked."
-tags: ["testing","engineering"]
+description: "Org role guidance for an evidence collector: verify claimed work with screenshots, command output and spec-vs-evidence tables before anything is marked done."
+tags: ["testing","engineering","audit"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/experiment-designer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: experiment-designer
-description: "Use when planning product experiments, writing testable hypotheses, estimating sample size, prioritizing tests, or interpreting A/B outcomes with practical statistical rigor."
-tags: ["product","data"]
+description: "Use when planning a product A/B or multivariate test: If/Then/Because hypotheses, primary and guardrail metrics, sample size and MDE, ICE prioritization. For logging and reproducing ML runs use experiment-tracker; for scientific study design use experimental-design."
+tags: ["product","data","experimentation","statistics"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/experiment-tracker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: experiment-tracker
-description: "Experiment Tracker role best practices. Records and organizes every experiment (ML training run, A/B test, feature trial) — parameters, code version, data, environment, and results — so outcomes are reproducible, comparable, and auditable."
-tags: ["ai-ml","engineering"]
+description: "Use when an org role acts as experiment tracker and must log every ML run or A/B test with params, code, data and environment so results are reproducible. Covers MLflow or W&B style tracking and decision records; for designing product A/B tests use experiment-designer."
+tags: ["ai-ml","engineering","experimentation","evaluation"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/experimental-design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: experimental-design
-description: "Design experiments and studies BEFORE data is collected — choosing a design, randomizing, blocking, and laying out treatment combinations so results are interpretable."
-tags: ["science","research","data"]
+description: "Use when designing a scientific study before data collection: randomization, blocking, replication, factorial and response-surface DOE layouts with pyDOE3. Covers crossover, split-plot, cluster and adaptive designs; for product A/B tests use experiment-designer."
+tags: ["science","research","data","statistics","experimentation"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/fastapi-expert/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: fastapi-expert
-description: "Use when building high-performance async Python APIs with FastAPI and Pydantic V2. Invoke to create REST endpoints, define Pydantic models, implement authentication flows, set up async SQLAlchemy database operations, add JWT authentication, build WebSocket endpoints, or generate OpenAPI documentation."
-tags: ["engineering","backend"]
+description: "Use when building an async Python API with FastAPI and Pydantic V2 end to end: endpoints, async database access, JWT auth, WebSockets and pytest tests. A persona with deep reference files; for a project-structure and idiom catalogue use fastapi-patterns."
+tags: ["engineering","backend","fastapi","python","api"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/fastapi-patterns/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: fastapi-patterns
-description: "FastAPI best practices covering project structure, Pydantic v2 schemas, dependency injection, async handlers, authentication, authorization, transactional service layers, and testing with httpx and pytest. Use when building or reviewing FastAPI apps — Pydantic schemas, dependencies, async handlers, auth, or tests."
-tags: ["backend"]
+description: "Use when structuring or reviewing a FastAPI codebase against idioms: app factory, Pydantic v2 schemas, dependency injection, service layers and httpx tests. A pattern catalogue; for building endpoints end to end with reference files use fastapi-expert."
+tags: ["backend","fastapi","python","architecture"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/feedback-synthesizer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: feedback-synthesizer
-description: "Feedback Synthesizer role best practices. Turns raw, scattered user feedback (interviews, surveys, support tickets, reviews) into actionable themes and recommendations — the bridge between \"we collected data\" and \"here's what to do about it.\""
-tags: ["product"]
+description: "Use when an org role acts as feedback synthesizer and must turn interviews, surveys, tickets and reviews into evidenced themes and prioritized recommendations."
+tags: ["product","customer-research","ux"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/finance-tracker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: finance-tracker
-description: "Finance Tracker role best practices. Keeps ongoing visibility into money in and out — expenses, budgets, and core financial KPIs — so decisions are made on current, accurate data rather than stale or informal impressions."
-tags: ["sales"]
+description: "Use when an org role acts as finance tracker and must keep expenses, budgets, budget-vs-actual variance, burn and cash runway current and auditable."
+tags: ["sales","finance","analytics"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/finishing-a-development-branch/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: finishing-a-development-branch
-description: "Use when implementation is complete, all tests pass, and you need to decide how to integrate the work"
-tags: ["engineering","devops"]
+description: "Use when implementation is done and tests pass and you must choose how to integrate a git branch or worktree: merge locally, open a PR or keep it. Verifies the suite, detects worktree state and cleans up afterwards."
+tags: ["engineering","devops","git"]
 tools: []
 license: MIT
 source: https://github.com/obra/superpowers

package/org-skills/flutter-expert/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: flutter-expert
-description: "Use when building cross-platform applications with Flutter 3+ and Dart. Invoke for widget development, Riverpod/Bloc state management, GoRouter navigation, platform-specific implementations, performance optimization."
-tags: ["engineering","mobile"]
+description: "Use when building a Flutter 3 and Dart app end to end: Riverpod or Bloc state, GoRouter, custom widgets and animations, tests and DevTools profiling. A persona with deep reference files; for a copy-paste Dart idiom catalogue use dart-flutter-patterns."
+tags: ["engineering","mobile","flutter","performance"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/focused-fix/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: focused-fix
-description: "Use when the user asks to fix, debug, or make a specific feature/module/area work end-to-end. Triggers: 'make X work', 'fix the Y feature', 'the Z module is broken', 'focus on [area]'. Not for quick single-bug fixes — this is for systematic deep-dive repair across all files and dependencies."
-tags: ["engineering"]
+description: "Use when a whole feature or module is broken and must work end to end: scope it, trace every dependency, diagnose all issues, then fix and verify. Triggers: 'make X work', 'fix the Y feature', 'the Z module is broken'; for a single bug use systematic-debugging."
+tags: ["engineering","debug","testing"]
 tools: ["monograph_query","monograph_context","monograph_impact","monograph_suggest"]
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/free-tool-strategy/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: free-tool-strategy
-description: "When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness."
-tags: ["marketing","product"]
+description: "Use when planning, evaluating or building a free tool as engineering-as-marketing for lead generation, SEO traffic or brand awareness."
+tags: ["marketing","product","growth","seo"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/frontend-design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: frontend-design
-description: "Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults."
-tags: ["frontend","design"]
+description: "Use when building or reshaping a web UI that needs a distinctive, subject-grounded visual identity: typography, color tokens, layout and restrained motion. Plans, critiques and avoids generated-page defaults; for ECC's lighter direction checklist use frontend-design-direction."
+tags: ["frontend","design","ui"]
 tools: ["monodesign_detect","monodesign_fix","monodesign_palette","monograph_query"]
 license: Apache-2.0
 source: https://github.com/anthropics/skills

package/org-skills/frontend-design-direction/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: frontend-design-direction
-description: "Set an ECC-specific frontend design direction for production UI work. Use when building or improving websites, dashboards, applications, components, landing pages, visual tools, or any web UI that needs stronger product-specific design judgment."
-tags: ["design","frontend"]
+description: "Use when a working web UI reads as generic and needs an explicit direction first: purpose, audience, tone and one memorable detail, before styling. ECC's design-direction checklist; for studio-style visual design guidance use frontend-design."
+tags: ["design","frontend","ui","ux"]
 tools: ["monodesign_detect","monodesign_fix","monodesign_palette"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/frontend-developer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: frontend-developer
-description: "Frontend Developer role best practices. Builds responsive, accessible, and performant web UIs with modern frameworks (React/Vue/Angular/Svelte) — turning designs into production-quality, maintainable interfaces."
-tags: ["frontend","engineering"]
+description: "Org role guidance for a frontend developer: build responsive, accessible web UIs in React, Vue, Angular or Svelte that meet Core Web Vitals. For React and Next.js code patterns use frontend-patterns."
+tags: ["frontend","engineering","accessibility","performance"]
 tools: ["monograph_query","monograph_context","monograph_impact","monodesign_detect","monodesign_fix","monodesign_palette"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/frontend-patterns/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: frontend-patterns
-description: "Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance."
-tags: ["frontend"]
+description: "Use when building or reviewing React and Next.js components: composition, state with Zustand or Context, SWR or React Query fetching, Zod forms and memoization. A broad pattern catalogue; for deeper React-only guidance see react-patterns or react-expert."
+tags: ["frontend","react","nextjs","typescript","performance"]
 tools: ["monograph_query","monograph_context","monodesign_detect"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/game-audio-engineer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: game-audio-engineer
-description: "Game Audio Engineer role best practices. Implements adaptive sound and music systems in-engine — building mixer architecture, middleware projects (Wwise/FMOD), and gameplay-driven audio parameters — not just producing sound assets."
-tags: ["design"]
+description: "Use when an org role acts as game audio engineer and must implement adaptive sound and music in-engine with Wwise or FMOD, mixer buses and gameplay parameters."
+tags: ["design","game-dev","performance"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/game-designer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: game-designer
-description: "Game Designer role best practices. Designs the core gameplay loop, mechanics, and balancing that make a game engaging — the systemic \"why is this fun\" layer that everything else (levels, narrative, art) builds on."
-tags: ["design"]
+description: "Use when an org role acts as game designer and must define the core gameplay loop, mechanics, difficulty balancing and game feel, validated by playtesting."
+tags: ["design","game-dev","ux"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/gdpr-data-handling/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: gdpr-data-handling
-description: "Implement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews."
-tags: ["legal","security"]
+description: "Use when building systems that process EU personal data under GDPR: lawful bases, consent management, data subject requests, privacy by design and DPAs."
+tags: ["legal","security","compliance"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/general-counsel-advisor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: general-counsel-advisor
-description: "General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA, fintech), or when user mentions general counsel, GC, legal review, contract..."
-tags: ["legal","leadership"]
+description: "Use when a startup founder or GC needs legal triage: contract review (MSA, SaaS, NDA, DPA, employment), IP ownership, term sheet terms and regulatory mapping. Includes contract risk and term sheet scanner scripts; not legal advice. For drafting contracts use contract-and-proposal-writer."
+tags: ["legal","leadership","compliance","fundraising"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/git-advanced-workflows/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: git-advanced-workflows
-description: "Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues."
-tags: ["engineering","devops"]
+description: "Use when rewriting or rescuing Git history: interactive rebase, cherry-pick, bisect, worktrees and reflog recovery of lost commits. For team branching strategy and commit conventions use git-workflow."
+tags: ["engineering","devops","git"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/git-workflow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: git-workflow
-description: "Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes. Use when choosing a branching strategy, writing commit conventions, deciding merge versus rebase, or resolving conflicts."
-tags: ["engineering","devops"]
+description: "Use when choosing a team Git workflow: GitHub flow, trunk-based or GitFlow branching, commit conventions, merge vs rebase, conflict resolution and release tags. For history surgery like bisect or reflog use git-advanced-workflows."
+tags: ["engineering","devops","git"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/golang-patterns/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: golang-patterns
-description: "Idiomatic Go patterns, best practices, and conventions for building robust, efficient, and maintainable Go applications. Use when writing or reviewing Go code and idiomatic structure or conventions are in question."
-tags: ["engineering","backend"]
+description: "Use when writing, reviewing or refactoring Go code for idiomatic structure: error wrapping, small interfaces, goroutine coordination and package design."
+tags: ["engineering","backend","go","coding-standards"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/golang-pro/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: golang-pro
-description: "Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming, microservices architecture, or high-performance systems."
-tags: ["engineering","backend"]
+description: "Use when building Go services end to end: goroutine and channel concurrency, gRPC or REST microservices, generics, pprof profiling and race-tested table tests. A senior-Go persona with reference files on concurrency, interfaces, generics, testing and module layout."
+tags: ["engineering","backend","go","performance"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/harness-engineering/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: harness-engineering
-description: "This skill should be used when designing autonomous agent harnesses: research loops, evaluation scaffolds, locked and editable surfaces, durable logs, novelty gates, pruning, rollback, PR preparation, and human approval boundaries."
-tags: ["ai-ml","engineering"]
+description: "Use when designing the control harness around an autonomous agent: locked vs editable surfaces, durable logs, novelty gates, rollback and human approval. Covers autoresearch-style loops and PR-producing background agents. Not for tool schemas (agent-tool-design) or project-level pipeline planning (llm-project-development)."
+tags: ["ai-ml","engineering","agents","evaluation"]
 tools: []
 license: MIT
 source: https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering

package/org-skills/healthcare-phi-compliance/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: healthcare-phi-compliance
-description: "Protected Health Information (PHI) and Personally Identifiable Information (PII) compliance patterns for healthcare applications. Covers data classification, access control, audit trails, encryption, and common leak vectors. Use when code touches PHI or PII in a healthcare system, or when auditing access control, audit trails, or leak vectors."
-tags: ["legal","security","engineering"]
+description: "Use when code touches patient PHI or PII in a healthcare system: data classification, Postgres row-level security, tamper-proof audit trails and leak vectors. Applies to HIPAA, GDPR and DISHA; covers error messages, logs and URLs as common leak paths."
+tags: ["legal","security","engineering","compliance","postgres"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/hexagonal-architecture/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: hexagonal-architecture
-description: "Design, implement, and refactor Ports & Adapters systems with clear domain boundaries, dependency inversion, and testable use-case orchestration across TypeScript, Java, Kotlin, and Go services. Use when introducing or refactoring toward Ports and Adapters, or when domain logic has become entangled with I/O."
-tags: ["engineering","backend"]
+description: "Use when introducing or refactoring toward Ports and Adapters: ports, adapters, a composition root and per-boundary tests in TypeScript, Java, Kotlin or Go. A focused step-by-step guide to one pattern; for Clean Architecture and DDD together, see architecture-patterns."
+tags: ["engineering","backend","architecture","refactor"]
 tools: ["monograph_query","monograph_context","monograph_impact","monograph_suggest"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/hierarchical-coord/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: hierarchical-coord
-description: "Hierarchical Coordinator role best practices. Runs a manager/worker tree: owns authoritative state, decomposes objectives into subtasks with a single accountable owner each, and reconciles reports flowing back up the chain."
-tags: ["operations"]
+description: "Use when an org role acts as hierarchical coordinator and must run a manager/worker tree: decompose goals into owned subtasks and reconcile reports upward. Differs from queen-coordinator by covering multi-level trees, when to stay flat, and drift intervention."
+tags: ["operations","coordination","agents","planning"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/huggingface-transformers/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: huggingface-transformers
-description: "Hugging Face Transformers for loading Hub models, running pipeline inference, text generation, and Trainer fine-tuning on NLP, vision, audio, and multimodal tasks. Use when working with AutoModel, pipelines, tokenizers, or TrainingArguments—not for general ML outside the Transformers library."
-tags: ["ai-ml","engineering"]
+description: "Use when working with the Hugging Face Transformers library in Python: loading Hub models, pipelines, tokenizers, text generation and Trainer fine-tuning. Covers NLP, vision, audio and multimodal tasks on Transformers v5 (PyTorch-only), Hub auth and caching; not for general ML outside Transformers."
+tags: ["ai-ml","engineering","python","llm"]
 tools: []
 license: Apache-2.0
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/hypothesis-generation/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: hypothesis-generation
-description: "Formulate evidence-bounded scientific questions, candidate hypotheses, rival explanations, causal or associational claims, discriminating predictions, measurements, and preregistration-ready analysis plans. Use when turning observations or preliminary findings into transparent, testable research plans without treating hypotheses as facts."
-tags: ["research","science"]
+description: "Use when turning observations into testable scientific hypotheses: rival explanations, causal estimands, predictions and preregistration-ready analysis plans. Includes safety and ethics gates and keeps observation, hypothesis, prediction and evidence strictly distinct."
+tags: ["research","science","statistics","experimentation"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/incident-command-playbook/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: incident-command-playbook
-description: "Comprehensive incident response framework from detection through resolution and post-incident review. Battle-tested SRE/DevOps practices: severity classification, timeline reconstruction, structured post-incident analysis. Use when declaring an incident, coordinating multi-team response during an outage, leading a post-mortem, or setting up on-call practices for a new service."
-tags: ["operations","devops"]
+description: "Use when declaring or running an availability incident (outage, degradation, failed deploy): SEV1-SEV4 triage, timeline reconstruction and post-incident review. Imported playbook with Python classifier, timeline and PIR generator scripts; not for security incidents. For the org-role persona, see incident-commander."
+tags: ["operations","devops","incident","reliability"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/incident-commander/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: incident-commander
-description: "Incident Commander role best practices. Turn production chaos into structured, time-boxed resolution — classify severity, assign clear roles, drive communication cadence, and convert every incident into a systemic fix via blameless post-mortem."
-tags: ["devops"]
+description: "Use when an org role acts as incident commander and must drive a production incident: set severity, assign roles, run comms and lead a blameless post-mortem. Short role guidance; for the full playbook with scripts use incident-command-playbook, for writing runbooks use incident-runbook-templates."
+tags: ["devops","incident","reliability","communication"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/incident-runbook-templates/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: incident-runbook-templates
-description: "Create structured incident response runbooks with step-by-step procedures, escalation paths, and recovery actions. Use this skill when building a service outage runbook for a payment processing system; creating database incident procedures covering connection pool exhaustion, replication lag, and disk space alerts;"
-tags: ["operations","devops"]
+description: "Use when writing incident runbooks for a service: detection, triage, mitigation, rollback, escalation matrix and communication templates. Authoring templates, not live incident command (see incident-commander). Includes worked database and Kubernetes examples."
+tags: ["operations","devops","incident","documentation","reliability"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/influencer-marketing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: influencer-marketing
-description: "When the user wants to run influencer, creator, or ambassador partnerships to promote their product — finding and vetting partners, structuring deals, briefing creators, disclosure compliance, and measuring ROI."
-tags: ["marketing"]
+description: "Use when running influencer, creator or ambassador partnerships: vetting partners, structuring flat, CPA or hybrid deals, briefs, disclosure and ROI. Covers B2C (Instagram, TikTok, YouTube) and B2B creators (LinkedIn, newsletters, podcasts)."
+tags: ["marketing","social","growth"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/infrastructure/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: infrastructure
-description: "Infrastructure role best practices. Designs and operates the underlying systems (compute, networking, storage, CI/CD) that everything else runs on — reliability and reproducibility over feature velocity."
-tags: ["devops"]
+description: "Use when an org role acts as infrastructure engineer and must design and operate compute, networking, storage and CI/CD as reproducible infrastructure as code. Covers Terraform or Pulumi plan/apply review, well-architected trade-offs, right-sizing and monitoring before incidents."
+tags: ["devops","cloud","terraform","reliability"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/input-validator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: input-validator
-description: "Input Validator role best practices. Enforces that every value crossing a trust boundary — user input, API payload, file upload, env var — is checked against an explicit allowlist before it reaches business logic."
-tags: ["security"]
+description: "Use when an org role acts as input validator and must enforce allowlist checks on every value crossing a trust boundary: input, payloads, uploads, env vars. Covers validation vs sanitization, schema libraries (Zod, Pydantic, JSON Schema), output encoding and fuzzing."
+tags: ["security","api","code-review"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/intent-driven-development/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: intent-driven-development
-description: "Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable."
-tags: ["engineering","product"]
+description: "Use when a feature or high-risk change (auth, data, migration, external API) needs scoped, verifiable acceptance criteria before or alongside implementation. Produces Quick Capture or Full Acceptance Briefs with AC-NNN criteria and handles revisions; lighter-weight and risk-scaled compared with spec-driven-workflow."
+tags: ["engineering","product","planning"]
 tools: ["monograph_suggest"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/inventory-demand-planning/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: inventory-demand-planning
-description: "Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC/XYZ analysis, seasonal transition management, and vendor negotiation frameworks."
-tags: ["operations","data"]
+description: "Use when forecasting retail demand or setting inventory policy: forecast method choice, ABC/XYZ analysis, safety stock, reorder points and promotional lift. Written for multi-location retailers; covers MAPE and bias tracking, MOQ/EOQ and seasonal transitions."
+tags: ["operations","data","supply-chain","statistics"]
 tools: []
 license: Apache-2.0
 source: https://github.com/affaan-m/ECC

package/org-skills/investor-materials/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: investor-materials
-description: "Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets."
-tags: ["finance","writing"]
+description: "Use when creating or updating pitch decks, one-pagers, investor memos, accelerator applications, financial models or use-of-funds tables. Enforces one source of truth so every fundraising document agrees on metrics, raise size and milestones."
+tags: ["finance","writing","fundraising"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/ios-developer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ios-developer
-description: "iOS Developer role best practices. Builds native iOS applications with Swift and SwiftUI — modern, safe, performant apps that follow Apple's current platform conventions and data-safety guarantees."
-tags: ["frontend","engineering"]
+description: "Use when an org role acts as iOS developer and must build native apps in Swift and SwiftUI with @Observable state, strict concurrency, SwiftData and Keychain. Short role guidance on Apple conventions and accessibility; for deep Swift reference material use swift-expert."
+tags: ["frontend","engineering","swift","mobile"]
 tools: ["monograph_query","monograph_context","monograph_impact","monodesign_detect","monodesign_fix","monodesign_palette"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/isms-audit-expert/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: isms-audit-expert
-description: "Information Security Management System (ISMS) audit expert for ISO 27001 compliance verification, security control assessment, and certification support. Use when the user mentions ISO 27001, ISMS audit, Annex A controls, Statement of Applicability (SOA), gap analysis, nonconformity management, internal audit, surveillance audit, or security certification preparation."
-tags: ["security","legal"]
+description: "Use when planning or running an ISO 27001 ISMS audit: risk-based audit schedules, Annex A control assessment, Statement of Applicability and nonconformities. Auditor-side procedures, versus compliance-auditor, which is org role guidance across SOC 2, HIPAA and PCI-DSS."
+tags: ["security","legal","audit","compliance"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/issue-tracker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: issue-tracker
-description: "Issue Tracker role best practices. Keep issues accurate, well-triaged, and actionable — the single source of truth for what work exists, its state, and who owns it."
-tags: ["engineering","devops"]
+description: "Org role guidance for an issue tracker: keep issues accurate, triaged, labeled and linked to PRs as the source of truth for work and ownership. Covers gh issue workflows, templates, milestones and duplicate search."
+tags: ["engineering","devops","planning","git"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/java-architect/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: java-architect
-description: "Use when building, configuring, or debugging enterprise Java applications with Spring Boot 3.x, microservices, or reactive programming. Invoke to implement WebFlux endpoints, optimize JPA queries and database performance, configure Spring Security with OAuth2/JWT, or resolve authentication issues and async processing challenges in cloud-native Spring applications."
-tags: ["engineering","backend"]
+description: "Use when building or debugging enterprise Java 21 apps on Spring Boot 3: microservices, WebFlux endpoints, JPA query tuning and Spring Security OAuth2/JWT. A persona with reference files on setup, reactive, JPA, security and testing; for style rules see java-coding-standards."
+tags: ["engineering","backend","java","spring"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/java-coding-standards/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: java-coding-standards
-description: "Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout. Automatically applies framework-specific conventions. Use when writing or reviewing Java in a Spring Boot or Quarkus service."
-tags: ["engineering","backend"]
+description: "Use when writing or reviewing Java 17+ code in Spring Boot or Quarkus for naming, immutability, Optional, streams, exceptions, generics and project layout. Detects the framework from the build file and applies Spring or Quarkus (CDI, Panache) conventions; a style guide, not an architecture guide."
+tags: ["engineering","backend","java","coding-standards","spring"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC