@monoes/monomindcli 2.16.1 → 2.16.3

package/org-skills/bash-defensive-patterns/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: bash-defensive-patterns
-description: "Master defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety."
-tags: ["devops","engineering"]
+description: "Use when writing production Bash scripts, CI scripts or system utilities that must fail safely: strict mode, quoting, traps and input checks. Also covers mktemp cleanup, structured logging, dry-run and idempotency."
+tags: ["devops","engineering","bash"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/before-you-build/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: before-you-build
-description: "Pre-build product and feature risk review for founders, product managers, and AI-assisted builders. Use this skill when the user is about to build a landing page, MVP, SaaS product, internal tool, agent workflow, or major feature and needs to check demand, positioning, monetization, retention, trust, distribution, and adoption risk before implementation starts."
-tags: ["product"]
+description: "Use when about to build an MVP, SaaS product, landing page, agent workflow or major feature and need a quick pre-mortem on demand and adoption risk. Checks positioning, monetization, retention, trust and distribution, returning a short verdict and the smallest validation step."
+tags: ["product","planning","strategy"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/benchmark-methodology/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: benchmark-methodology
-description: "Use after competitive-platform-analysis has produced a tiered competitor set. Scores each competitor across nine weighted dimensions (positioning, voice, visual craft, offer packaging, evidence, enterprise-readiness, thought leadership, pricing, client's strategic tension) with explicit 1 to 5 rubrics and a tension-plot. Precedes competitive-report-structure."
-tags: ["research","marketing"]
+description: "Use when scoring a scoped competitor set on nine weighted dimensions with 1-5 rubrics and a strategic-tension plot, producing profile cards. Second step of the competitive pipeline, after competitive-platform-analysis and before competitive-report-structure."
+tags: ["research","marketing","competitive-analysis"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/benchmarker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: benchmarker
-description: "Benchmarker role best practices. Designs and runs load, stress, and regression benchmarks that produce statistically trustworthy, reproducible performance numbers — and turns them into clear pass/fail verdicts against defined targets."
-tags: ["engineering"]
+description: "Use when an org role acts as benchmarker and must design and run load, stress and regression benchmarks that give reproducible pass or fail verdicts. Warm-up, repeated trials, p95 and p99 thresholds and baselines, with k6, Locust or Gatling and CI regression gates."
+tags: ["engineering","performance","testing"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/blockchain-auditor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: blockchain-auditor
-description: "Blockchain Auditor role best practices. Audits smart contracts and DeFi protocols for exploitable vulnerabilities — combining automated analysis, manual review, and economic attack modeling — before attackers find the bugs first."
-tags: ["engineering","security"]
+description: "Use when an org role acts as blockchain auditor and must audit smart contracts and DeFi protocols for fund-loss vulnerabilities before attackers do. Manual review plus Slither, Mythril, fuzzing and economic attack modeling, with PoCs and honest severity; for general app security use security-auditor."
+tags: ["engineering","security","blockchain","audit"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/board-deck-builder/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: board-deck-builder
-description: "Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes."
-tags: ["leadership","finance","writing"]
+description: "Use when assembling a board or investor update deck: executive summary, metrics table, financials, per-function sections, bad-news delivery and asks. Pulls C-suite perspectives into one narrative and never invents numbers."
+tags: ["leadership","finance","writing","fundraising","communication"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/business-investment-advisor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: business-investment-advisor
-description: "Business investment analysis and capital allocation advisor. Use when evaluating whether to invest in equipment, real estate, a new business, hiring, technology, or any capital expenditure. Also use for ROI calculations, IRR, NPV, payback period, build vs buy decisions, lease vs buy analysis, vendor evaluation, or deciding where to allocate limited budget for maximum return."
-tags: ["finance"]
+description: "Use when evaluating a business capital decision (equipment, hire, software, real estate, new line) with ROI, NPV, IRR and payback. Also build vs buy, lease vs buy and allocating a limited budget; not for personal stock or securities advice."
+tags: ["finance","strategy","planning"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

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

@@ -1,7 +1,7 @@
 ---
 name: byzantine-coord
-description: "Byzantine Coordinator role best practices. Coordinates agreement among agents when some participants may be faulty, malicious, or reporting contradictory information — not just slow or offline."
-tags: ["operations"]
+description: "Use when an org role acts as Byzantine coordinator and must reach agreement among agents that may be faulty, malicious or contradictory. Uses n of at least 3f+1, 2/3+ quorums, multi-phase commit and signed audit logs; for choosing among mechanisms see consensus-coordinator."
+tags: ["operations","coordination","agents","reliability"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: canvas-design
-description: "Create beautiful visual art in .png and .pdf documents using design philosophy. Use when asked to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations."
-tags: ["design","marketing"]
+description: "Use when creating an original static visual piece (poster, artwork, design) as a PNG or PDF by first writing a design philosophy, then expressing it visually. Mostly visual, minimal text; never copies existing artists."
+tags: ["design","marketing","ui"]
 tools: []
 license: Apache-2.0
 source: https://github.com/anthropics/skills

package/org-skills/carrier-relationship-management/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: carrier-relationship-management
-description: "Codified expertise for managing carrier portfolios, negotiating freight rates, tracking carrier performance, allocating freight, and maintaining strategic carrier relationships. Informed by transportation managers with 15+ years experience. Includes scorecarding frameworks, RFP processes, market intelligence, and compliance vetting."
-tags: ["operations"]
+description: "Use when managing freight carrier portfolios: FMCSA vetting and onboarding, lane RFPs, rate and fuel-surcharge negotiation, scorecards and routing guides. For shipment delays, damages and claims use logistics-exception-management."
+tags: ["operations","supply-chain","strategy"]
 tools: []
 license: Apache-2.0
 source: https://github.com/affaan-m/ECC

package/org-skills/case-analyst/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: case-analyst
-description: "Case Analyst role best practices. Performs neutral, systematic case evaluation and legal research — gathers facts, maps applicable law, identifies precedent, and surfaces risks and weaknesses for whichever party or process consumes the analysis."
-tags: ["legal"]
+description: "Use when an org role acts as case analyst and must neutrally evaluate a legal matter: facts, applicable law, precedent hierarchy and risks on both sides. Research with cited sources, flagging ambiguity rather than advocating."
+tags: ["legal","research","audit"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/ceo-advisor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ceo-advisor
-description: "Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, fundraising, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive..."
-tags: ["leadership"]
+description: "Use when a CEO or founder needs executive guidance on strategy, capital allocation, fundraising, board and investor management, culture or major decisions. Includes strategy and scenario scripts; for finance-specific depth use cfo-advisor."
+tags: ["leadership","strategy","fundraising"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/cfo-advisor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: cfo-advisor
-description: "Financial leadership for startups and scaling companies. Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages. Use when building financial models, analyzing unit economics, planning fundraising, managing cash runway, preparing board materials, or when user mentions CFO, burn rate, runway, fundraising, unit economics, LTV, CAC, term sheets, or..."
-tags: ["leadership","finance"]
+description: "Use when a startup finance leader needs burn and runway scenarios, cohort unit economics, fundraising and dilution modeling, or board financial packages. Strategic CFO frameworks with scripts for LTV, CAC and payback; for detailed 3-5 year projections use startup-financial-modeling."
+tags: ["leadership","finance","fundraising","strategy"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/change-management/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: change-management
-description: "Framework for rolling out organizational changes without chaos. Covers the ADKAR model adapted for startups, communication templates, resistance patterns, and change fatigue management. Handles process changes, org restructures, strategy pivots, and culture changes."
-tags: ["leadership","operations"]
+description: "Use when rolling out an org change (reorg, process or tool migration, strategy pivot, culture change) using ADKAR adapted for startups. Covers communication templates, resistance patterns and change fatigue."
+tags: ["leadership","operations","people","communication"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/changelog-automation/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: changelog-automation
-description: "Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions."
-tags: ["engineering","devops","writing"]
+description: "Use when automating changelogs and release notes from commits and PRs with Keep a Changelog, Conventional Commits and semantic versioning. Tooling and format, including GitHub or GitLab release notes; for coordinating a release as an org role see release-manager."
+tags: ["engineering","devops","writing","git","documentation"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/chro-advisor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: chro-advisor
-description: "People leadership for scaling companies. Hiring strategy, compensation design, org structure, culture, and retention. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building culture, or when user mentions CHRO, HR, people strategy, talent, headcount, compensation, org design, retention, or performance management."
-tags: ["leadership","operations"]
+description: "Use when a people leader needs headcount planning, compensation bands and equity, org design, performance calibration or retention strategy. Includes hiring-plan and comp scripts for scaling companies; for early-stage team and equity design see team-composition-analysis."
+tags: ["leadership","operations","people"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/churn-prevention/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: churn-prevention
-description: "When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies."
-tags: ["marketing","product","support"]
+description: "Use when reducing SaaS churn: cancellation flows, save offers, exit surveys, dunning and failed-payment recovery, and retention strategy. Treats voluntary and involuntary churn separately, with billing tools like Stripe, Chargebee or Paddle."
+tags: ["marketing","product","support","growth"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/cicd-engineer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: cicd-engineer
-description: "CI/CD Engineer role best practices. Build and operate the pipelines that take code from commit to production — fast enough that developers don't dread them, safe enough that bad code rarely ships, observable enough that failures are easy to diagnose."
-tags: ["devops"]
+description: "Use when an org role acts as CI/CD engineer and must build and run commit-to-production pipelines that are fast, gated and reversible. Covers pipeline-as-code, quality and security gates, caching, canary or blue-green rollout and one-command rollback."
+tags: ["devops","deploy","reliability"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/ciso-advisor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ciso-advisor
-description: "Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), security architecture strategy, incident response leadership, and board-level security reporting."
-tags: ["leadership","security"]
+description: "Use when a security leader needs risk quantified in dollars, a SOC 2, ISO 27001, HIPAA or GDPR roadmap, or board-level security reporting. Also zero-trust strategy and IR leadership; strategic, not hands-on audits, for controls and evidence work see compliance-auditor."
+tags: ["leadership","security","compliance","strategy"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/click-path-audit/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: click-path-audit
-description: "Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores."
-tags: ["frontend","testing"]
+description: "Use when users report broken buttons that code review cannot explain: trace each UI handler's state writes and side effects to find calls that undo each other. Covers Zustand, Redux and React context stores and race conditions, also after refactors touching shared state."
+tags: ["frontend","testing","debug","react"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

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

@@ -1,7 +1,7 @@
 ---
 name: cloud-architect
-description: "Cloud Architect role best practices. Designs cloud system architecture — service topology, networking, and provider-specific patterns — balancing reliability, security, performance, and cost across AWS/GCP/Azure."
-tags: ["devops"]
+description: "Use when an org role acts as cloud architect and must design service topology, networking and multi-AZ resilience across AWS, GCP or Azure. Role guidance on explicit cost and reliability trade-offs; for migrations, DR and provider reference files use cloud-architecture."
+tags: ["devops","cloud","architecture"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: cloud-architecture
-description: "Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments."
-tags: ["devops","engineering"]
+description: "Use when designing AWS, Azure or GCP architectures, planning migrations with the 6Rs, setting DR with RTO and RPO checks, or cutting cloud costs. Persona workflow with per-provider references and CLI validation steps; for pure cost work see cost-optimization."
+tags: ["devops","engineering","cloud","architecture","migrate"]
 tools: []
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/cmo-advisor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: cmo-advisor
-description: "Marketing leadership for scaling companies. Brand positioning, growth model design, marketing budget allocation, and marketing org design. Use when designing brand strategy, selecting growth models (PLG vs sales-led vs community-led), allocating marketing budgets, building marketing teams, or when user mentions CMO, brand strategy, growth model, CAC, LTV, channel mix, or marketing ROI."
-tags: ["leadership","marketing"]
+description: "Use when a marketing leader needs brand positioning, a growth model choice (PLG, sales-led, community-led), channel budget allocation or marketing org design. Strategy, not campaign execution or content creation."
+tags: ["leadership","marketing","strategy","growth"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

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

@@ -1,7 +1,7 @@
 ---
 name: co-marketing
-description: "When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referral-programs."
-tags: ["marketing"]
+description: "Use when finding co-marketing partners, scoring partner fit, or planning joint campaigns, integration marketing and co-branded launches. For customer referral programs use referral-programs."
+tags: ["marketing","growth","strategy"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/code-documenter/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: code-documenter
-description: "Generates, formats, and validates technical documentation — including docstrings, OpenAPI/Swagger specs, JSDoc annotations, doc portals, and user guides. Use when adding docstrings to functions or classes, creating API documentation, building documentation sites, or writing tutorials and user guides. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, getting started guides."
-tags: ["engineering","writing"]
+description: "Use when adding docstrings, JSDoc or OpenAPI specs to code, or building doc sites and developer guides, with examples validated by doctest, tsc or Redocly lint. Documents existing code and reports coverage."
+tags: ["engineering","writing","documentation"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/code-review-swarm/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: code-review-swarm
-description: "Code Review Swarm role best practices. Run multi-angle code review — security, performance, style, and architecture — as coordinated specialist passes rather than one generalist skim, and turn findings into actionable, prioritized feedback."
-tags: ["engineering","devops"]
+description: "Use when an org role runs a multi-pass code review split by concern (security, performance, style, architecture) and merges findings into one review. Diff-scoped with block, warn or suggest severities; for a single-reviewer workflow see code-reviewer."
+tags: ["engineering","devops","code-review"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/code-reviewer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: code-reviewer
-description: "Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback."
-tags: ["engineering","testing"]
+description: "Org role guidance for a code reviewer: review PRs for bugs, security holes, N+1 queries and design issues, then write a structured, prioritized report. Workflow with checklist, feedback and spec-compliance references."
+tags: ["engineering","testing","code-review"]
 tools: ["monograph_query","monograph_context","monograph_impact","monograph_suggest"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/coder/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: coder
-description: "Coder role best practices. Implements features and fixes to spec — clean, correct, maintainable code that matches the existing codebase's conventions."
-tags: ["engineering"]
+description: "Org role guidance for a coder: implement features and fixes to spec, matching the codebase's existing conventions. Surgical diffs, explicit error handling, tests alongside the change, and running build and lint before declaring done."
+tags: ["engineering","coding-standards","testing"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: coding-standards
-description: "Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies."
-tags: ["engineering"]
+description: "Use when reviewing code quality or naming with no framework-specific skill: naming, readability, immutability, KISS, DRY, YAGNI and code smells. Cross-language floor; for C++ or Java rules use cpp-coding-standards or java-coding-standards."
+tags: ["engineering","coding-standards","code-review"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/cold-email/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: cold-email
-description: "Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails."
-tags: ["sales","writing"]
+description: "Use when writing B2B cold outreach and follow-up sequences (SDR and prospecting emails) that read like a peer and earn replies. For lifecycle and drip email flows use email-sequences."
+tags: ["sales","writing","email","copywriting"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

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

@@ -1,7 +1,7 @@
 ---
 name: collective-coord
-description: "Collective Intelligence Coordinator role best practices. Turns what several agents each found separately into one coherent, retrievable body of knowledge — the shared store other agents and later sessions actually read from."
-tags: ["operations"]
+description: "Use when an org role acts as collective intelligence coordinator and must merge what several agents found into one reconciled, retrievable knowledge store. Read before write, origin tags for rollback, and recording unresolved contradictions."
+tags: ["operations","coordination","agents"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: community-marketing
-description: "Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists."
-tags: ["marketing","support"]
+description: "Use when building or growing a product community on Discord, Slack, Circle, Reddit or forums to drive community-led growth, advocacy and word of mouth. Covers identity, member value and the community flywheel."
+tags: ["marketing","support","growth","social"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/competitive-landscape/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: competitive-landscape
-description: "Analyze competition, identify differentiation opportunities, and develop winning market positioning strategies using Porter's Five Forces, Blue Ocean Strategy, and positioning maps. Use this skill when evaluating competitors, assessing market positioning, identifying sustainable competitive advantages, or preparing competitive strategy analysis for a startup or investor pitch."
-tags: ["research","marketing","product"]
+description: "Use when analyzing market competition with Porter's Five Forces, Blue Ocean Strategy and positioning maps to find differentiation and defensible advantage. Market-level strategy; for product-level teardowns use competitive-teardown."
+tags: ["research","marketing","product","competitive-analysis","strategy"]
 tools: []
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/competitive-platform-analysis/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: competitive-platform-analysis
-description: "Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong to, and which sources to mine. First step in the three-skill competitive pipeline; precedes benchmark-methodology."
-tags: ["research","marketing"]
+description: "Use when scoping who counts as a competitor: tiering Direct, Adjacent and Aspirational rivals from a positioning brief and choosing sources. First step of the competitive pipeline, before benchmark-methodology."
+tags: ["research","marketing","competitive-analysis"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/competitive-report-structure/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: competitive-report-structure
-description: "Use after benchmark-methodology has produced scored competitor profile cards. Assembles findings into a decision-grade report: landscape map, competitor profiles, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Final step in the three-skill competitive pipeline."
-tags: ["research","writing"]
+description: "Use when assembling scored competitor cards into a decision-grade report: landscape map, profiles, benchmark matrix, white space and recommendations. Final step of the competitive pipeline, after benchmark-methodology."
+tags: ["research","writing","competitive-analysis"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/competitive-teardown/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: competitive-teardown
-description: "Analyzes competitor products and companies by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices scored across 12 dimensions, SWOT analyses, positioning maps, UX audits, pricing model breakdowns, action item roadmaps, and stakeholder presentation templates."
-tags: ["product","research","marketing"]
+description: "Use when tearing down specific competitor products from pricing pages, reviews, job posts, SEO and social signals into structured intelligence. Produces a 12-dimension scorecard, feature matrix, SWOT and action plan; for market-level strategy use competitive-landscape."
+tags: ["product","research","marketing","competitive-analysis"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/competitor-comparison-pages/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: competitor-comparison-pages
-description: "When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.'"
-tags: ["marketing","writing","sales"]
+description: "Use when creating competitor comparison or alternative pages ('X vs Y', 'X alternatives') for SEO and sales enablement, including battle cards. Honest, depth-first page content; for researching the competitors use competitive-teardown."
+tags: ["marketing","writing","sales","seo","competitive-analysis"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/compliance-auditor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: compliance-auditor
-description: "Compliance Auditor role best practices. Guides organizations through the technical/operational side of security certifications (SOC 2, ISO 27001, HIPAA, PCI-DSS) — controls implementation, evidence collection, and audit readiness — not legal interpretation."
-tags: ["security"]
+description: "Org role guidance for a compliance auditor: drive SOC 2, ISO 27001, HIPAA or PCI-DSS readiness through gap assessments and evidence collection. Covers cross-framework control mapping and automated evidence; operational side, not legal interpretation."
+tags: ["security","compliance","audit"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/consensus-coordinator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: consensus-coordinator
-description: "Consensus Coordinator role best practices. Picks and runs the right agreement mechanism for a given decision — vote tally, crash-fault-tolerant replication, or Byzantine-tolerant agreement — rather than defaulting to one protocol for every situation."
-tags: ["operations"]
+description: "Use when an org role acts as consensus coordinator and must pick the right agreement mechanism for a decision from its threat model. Chooses among threshold votes, Raft-style replication and Byzantine agreement; for running BFT itself see byzantine-coord."
+tags: ["operations","coordination","agents"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/content-creator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: content-creator
-description: "Content Creator role best practices. Produces and repurposes content across formats and platforms — turning one core idea into platform-native assets that build audience and drive measurable outcomes, not just volume."
-tags: ["writing","marketing"]
+description: "Use when an org role acts as content creator and must turn one core idea into platform-native assets across formats and platforms. Covers hooks, consistent voice and per-asset KPIs; for drafting specific posts and threads use content-engine."
+tags: ["writing","marketing","content","social"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/content-engine/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: content-engine
-description: "Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms."
-tags: ["marketing","writing"]
+description: "Use when writing X posts or threads, LinkedIn posts, short-form video or YouTube scripts, or repurposing one source asset across platforms. Source-first with voice kept intact; for planning what content to create use content-strategy."
+tags: ["marketing","writing","content","social"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/content-strategy/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: content-strategy
-description: "When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover."
-tags: ["marketing","writing"]
+description: "Use when planning a content strategy: what topics to cover, searchable vs shareable pieces, topic clusters, scoring and a content calendar. Planning, not drafting; for writing posts use content-engine or article-writing."
+tags: ["marketing","writing","content","strategy","seo"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/context-compression/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: context-compression
-description: "This skill should be used when long-running agent sessions need context compression, structured summarization, compaction, token-per-task optimization, or durable handoff summaries that preserve decisions, files, risks, and next actions."
-tags: ["ai-ml"]
+description: "Use when long agent sessions exceed context limits and need compaction: anchored iterative summaries, artifact-trail preservation and durable handoff summaries. For masking and caching tactics use context-optimization."
+tags: ["ai-ml","llm","agents"]
 tools: []
 license: MIT
 source: https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering

package/org-skills/context-degradation/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: context-degradation
-description: "This skill should be used for diagnosing and mitigating context degradation: lost-in-middle failures, context poisoning, context clash, context confusion, attention-pattern issues, and agent performance degradation caused by accumulated or conflicting context."
-tags: ["ai-ml"]
+description: "Use when diagnosing an LLM agent whose output degrades in long contexts: lost-in-middle, context poisoning, distraction, confusion or clash. Covers detection signals, recovery and placement strategy. For foundational concepts use context-fundamentals; for token-cost tactics use context-optimization."
+tags: ["ai-ml","llm","agents","debug"]
 tools: []
 license: MIT
 source: https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering

package/org-skills/context-fundamentals/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: context-fundamentals
-description: "This skill should be used to explain or reason about the foundational concepts of context engineering: what context is, the anatomy of a context window, how attention mechanics work, the U-shaped attention curve, why context quality matters more than quantity, and the mental models needed to interpret every other context-engineering decision."
-tags: ["ai-ml"]
+description: "Use when explaining or reasoning from first principles about LLM context engineering: context window anatomy, attention budget and the U-shaped attention curve. Conceptual only; for diagnosing active failures use context-degradation, for cost tactics use context-optimization."
+tags: ["ai-ml","llm","agents","prompting"]
 tools: []
 license: MIT
 source: https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering

package/org-skills/context-optimization/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: context-optimization
-description: "This skill should be used for improving context efficiency: context budgeting, observation masking, prefix or KV-cache strategy, partitioning, token-cost reduction, retrieval scoping, and extending effective context capacity without lowering answer quality."
-tags: ["ai-ml"]
+description: "Use when cutting LLM agent token cost or extending effective context: KV-cache prefix ordering, observation masking, compaction and sub-agent partitioning. For structured handoff summaries of a long session use context-compression; for diagnosing failures use context-degradation."
+tags: ["ai-ml","llm","agents","performance"]
 tools: []
 license: MIT
 source: https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering