@monoes/monomindcli 2.16.2 → 2.16.3

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

@@ -1,7 +1,7 @@
 ---
 name: queen-coordinator
-description: "Queen Coordinator role best practices. Same shape as a lead coordinator — decompose, delegate, hold authoritative state, decide when done — but scoped to a single bounded session with workers that report directly up to it and nowhere else."
-tags: ["operations"]
+description: "Use when an org role acts as queen coordinator and must decompose, delegate and reconcile work within one bounded session whose workers report only to it. Covers authoritative session state, capability routing, acceptance gates, drift correction and not overclaiming consensus. For a multi-level manager/worker tree, use hierarchical-coord."
+tags: ["operations","coordination","agents"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/quorum-manager/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: quorum-manager
-description: "Quorum Manager role best practices. Runs vote tallies over participating agents' votes and decides whether a proposal has met an explicit threshold — this is vote counting, not distributed consensus with leader election or fault tolerance."
-tags: ["operations"]
+description: "Org role guidance for a quorum manager: tally agent votes against an explicit majority, supermajority, unanimous or custom threshold and record the decision. Vote counting, not distributed consensus; covers roster denominators, double-vote checks, partial participation and signed audit records."
+tags: ["operations","coordination","agents"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/raft-manager/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: raft-manager
-description: "Raft Manager role best practices. Maintains a single authoritative, replicated log across participants via leader election and log replication — consensus under crash/omission faults, not malicious ones."
-tags: ["operations"]
+description: "Use when an org role acts as Raft manager and must keep one replicated log consistent via leader election and majority-committed replication. Covers randomized election timeouts, persisting term and vote, idempotent ops, split-brain tests and snapshotting; crash faults only, not Byzantine."
+tags: ["operations","coordination","reliability","architecture"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: rag-architect
-description: "Designs and implements production-grade RAG systems by chunking documents, generating embeddings, configuring vector stores, building hybrid search pipelines, applying reranking, and evaluating retrieval quality."
-tags: ["ai-ml","engineering"]
+description: "Use when designing or tuning a RAG system: document chunking, embeddings, vector stores like Pinecone, Qdrant or pgvector, hybrid search and reranking. Walks requirements through vector store design, retrieval pipeline and metrics with checkpoints."
+tags: ["ai-ml","engineering","llm","architecture","evaluation"]
 tools: []
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

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

@@ -1,7 +1,7 @@
 ---
 name: rails-patterns
-description: "Ruby on Rails framework patterns for Rails 7.1+ and 8.x apps. Covers the directory contract, skinny controllers with service objects, form objects, query objects, idiomatic ActiveRecord, background jobs, ViewComponent, Hotwire, and the Rails 8 Solid stack. Use when building or reviewing Rails apps, controllers, models, services, jobs, or views."
-tags: ["backend"]
+description: "Use when building or reviewing a Ruby on Rails 7 or 8 app: skinny controllers, service, form and query objects, ActiveRecord, jobs and Hotwire. A patterns catalogue for keeping app/ code conventional."
+tags: ["backend","architecture","coding-standards","api"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

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

@@ -1,7 +1,7 @@
 ---
 name: react-expert
-description: "Use when building React 18+ applications in .jsx or .tsx files, Next.js App Router projects, or create-react-app setups. Creates components, implements custom hooks, debugs rendering issues, migrates class components to functional, and implements state management. Invoke for Server Components, Suspense boundaries, useActionState forms, performance optimization, or React 19 features."
-tags: ["engineering","frontend"]
+description: "Use when building React 19 features end to end in TypeScript: components, hooks, Server Components, Next App Router, state and forms with actions. Persona with reference files and a tsc and Testing Library validation loop. For idiom review use react-patterns."
+tags: ["engineering","frontend","react","typescript","nextjs"]
 tools: ["monograph_query","monograph_context","monodesign_detect"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/react-native-expert/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: react-native-expert
-description: "Builds, optimizes, and debugs cross-platform mobile applications with React Native and Expo. Implements navigation hierarchies (tabs, stacks, drawers), configures native modules, optimizes FlatList rendering with memo and useCallback, and handles platform-specific code for iOS and Android."
-tags: ["engineering","mobile"]
+description: "Use when building, debugging or shipping a React Native and Expo app end to end: navigation, native modules, FlatList tuning and iOS or Android builds. Persona with reference files and error-recovery steps. For a catalogue of Expo patterns, use react-native-patterns."
+tags: ["engineering","mobile","react-native","debug"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

package/org-skills/react-native-patterns/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: react-native-patterns
-description: "React Native and Expo app patterns — Expo Router navigation, state separation (server/client/route/form), TanStack Query data fetching with Zod, performant lists, NativeWind/StyleSheet styling, native APIs, and secure storage. Use when building or editing React Native / Expo screens, components, navigation, or data layers."
-tags: ["mobile","frontend"]
+description: "Use when writing or reviewing Expo React Native screens: Expo Router, state placement, TanStack Query with Zod, lists, NativeWind and native APIs. A patterns catalogue; for an end-to-end build and debug persona, use react-native-expert."
+tags: ["mobile","frontend","react-native","typescript"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

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

@@ -1,7 +1,7 @@
 ---
 name: react-patterns
-description: "React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components."
-tags: ["frontend"]
+description: "Use when writing or reviewing React 18/19 components for idiom: hooks discipline, derived state, server/client boundaries, Suspense and form actions. A patterns catalogue; for perf rules use react-performance, for tests react-testing."
+tags: ["frontend","react","coding-standards","accessibility"]
 tools: ["monograph_query","monograph_context","monodesign_detect"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/react-performance/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: react-performance
-description: "React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance."
-tags: ["frontend"]
+description: "Use when a React or Next app is slow or a PR needs a perf pass: request waterfalls, bundle size, server rendering, re-renders and hydration. Organizes 70+ prioritized rules adapted from Vercel's React best practices. For general React idioms use react-patterns."
+tags: ["frontend","react","nextjs","performance"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/react-testing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: react-testing
-description: "React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages."
-tags: ["frontend","testing"]
+description: "Use when writing or fixing tests for React components and hooks with React Testing Library, Vitest or Jest, MSW network mocks and axe accessibility checks. Also decides what belongs in component tests vs Playwright or Cypress E2E. For browser E2E suites use playwright-expert."
+tags: ["frontend","testing","react","accessibility"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/reality-checker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: reality-checker
-description: "Reality Checker role best practices. Independently verifies that a reported outcome matches ground truth — catching agents or teammates that report success without having actually confirmed it."
-tags: ["testing","engineering"]
+description: "Use when an org role acts as reality checker and must independently verify a reported outcome against ground truth before it is accepted. Covers re-running tests and builds yourself, inspecting logs and data directly, spec-vs-observed tables, and treating unverified success claims as unconfirmed."
+tags: ["testing","engineering","audit","evaluation"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: receiving-code-review
-description: "Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation"
-tags: ["engineering"]
+description: "Use when you have received code review feedback and must decide how to act on it, especially if a suggestion seems unclear or wrong. Read, restate, verify against the codebase, then push back or implement one item at a time; no performative agreement. For reviewing others' code, use reviewer."
+tags: ["engineering","code-review","communication"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/obra/superpowers

package/org-skills/recruitment/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: recruitment
-description: "Recruitment role best practices. Sources, screens, and moves candidates through a hiring pipeline — for technical or general roles — balancing speed, candidate experience, and signal quality."
-tags: ["leadership","operations"]
+description: "Use when an org role acts as recruiter and must source, screen and move candidates through a hiring pipeline, balancing speed, candidate experience and signal. Covers role specs, referral channels, few purposeful interview stages, structured scorecards, fast feedback and stage conversion tracking."
+tags: ["leadership","operations","people"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: redis-patterns
-description: "Redis data structure patterns, caching strategies, distributed locks, rate limiting, pub/sub, and connection management for production applications. Use when adding caching, a distributed lock, rate limiting, or pub/sub with Redis, or when key design needs review."
-tags: ["data","backend"]
+description: "Use when adding Redis for caching, distributed locks, rate limiting, sessions, pub/sub or Streams, or tuning it for production. Covers data-structure choice, key design, cache-aside and other patterns, pooling, eviction and clustering."
+tags: ["data","backend","database","performance"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/referral-programs/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: referral-programs
-description: "When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.'"
-tags: ["marketing"]
+description: "Use when creating, optimizing or analyzing a customer referral, affiliate or ambassador program, or engineering word of mouth and viral loops. Covers incentive design, program fit, B2B vs B2C, LTV and CAC math and platform choice."
+tags: ["marketing","growth","strategy"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/release-manager/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: release-manager
-description: "Release Manager role best practices. Coordinate version bumps, changelogs, and deployment across one or more packages so releases are predictable, tested, and reversible."
-tags: ["engineering","devops"]
+description: "Org role guidance for a release manager: coordinate semver bumps, changelogs and staged deploys across monorepo packages so releases are reversible. Covers consistent internal versions, validation gates, rollback plans and gh release notes. For changelog tooling, use changelog-automation."
+tags: ["engineering","devops","deploy","git"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: repo-architect
-description: "Repo Architect role best practices. Design and maintain repository structure — directory layout, package boundaries, templates, and cross-repo conventions — so the codebase stays navigable and scalable as it grows."
-tags: ["engineering","devops"]
+description: "Org role guidance for a repo architect: design repository layout, package boundaries, shared configs and templates so a codebase stays navigable. Covers dependency direction, no circular deps, migration paths for restructures and synced issue/PR templates."
+tags: ["engineering","devops","architecture","git"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/researcher/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: researcher
-description: "Researcher role best practices. Investigates a codebase, technology, or question thoroughly and synthesizes findings into evidence-backed, actionable recommendations for other roles to act on."
-tags: ["engineering"]
+description: "Org role guidance for a researcher: investigate a codebase, technology or question and synthesize evidence-backed, cited recommendations for other roles. Covers broad-then-narrow search, cross-referencing sources, separating fact from inference, git history and flagging unknowns."
+tags: ["engineering","research","documentation"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/resource-allocator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: resource-allocator
-description: "Resource Allocator role best practices. Plans and adjusts compute/agent capacity ahead of demand — predicting resource needs from workload patterns and allocating (or scaling) accordingly, rather than reacting after saturation."
-tags: ["engineering"]
+description: "Org role guidance for a resource allocator: forecast compute or agent capacity from workload patterns and allocate or scale ahead of demand. Covers p90 provisioning, confidence thresholds, gradual rollout, multi-objective trade-offs, bulkhead isolation and allocation KPIs."
+tags: ["engineering","performance","planning","cloud"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: responsive-design
-description: "Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior."
-tags: ["design","frontend"]
+description: "Use when implementing responsive CSS layouts: mobile-first breakpoints, container queries, fluid typography, Grid and Flexbox, and responsive images. Covers touch targets, logical properties and common overflow issues."
+tags: ["design","frontend","ui","accessibility"]
 tools: ["monodesign_detect","monodesign_fix"]
 license: MIT
 source: https://github.com/wshobson/agents

package/org-skills/returns-reverse-logistics/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: returns-reverse-logistics
-description: "Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes."
-tags: ["operations"]
+description: "Use when running retail or e-commerce returns: RMA eligibility, condition grading, disposition routing, refunds, return fraud and warranty claims. Senior returns-manager persona with policy logic and recovery economics."
+tags: ["operations","supply-chain","support"]
 tools: []
 license: Apache-2.0
 source: https://github.com/affaan-m/ECC

package/org-skills/reviewer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: reviewer
-description: "Code Reviewer role best practices. Reviews code for correctness, security, maintainability, and performance — teaching through feedback, not gatekeeping style preferences."
-tags: ["engineering"]
+description: "Org role guidance for a code reviewer: review code for correctness, security, performance and maintainability with specific, severity-ranked feedback. Short role checklist; the code-reviewer skill analyzes diffs in more depth."
+tags: ["engineering","code-review","security"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/revops/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: revops
-description: "When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes."
-tags: ["sales","operations"]
+description: "Use when designing revenue operations: lead lifecycle stages, scoring and routing, marketing-to-sales handoff SLAs, CRM hygiene and funnel metrics. Covers PLG, sales-led and hybrid motions. For sales collateral use sales-enablement; for pricing use pricing-strategy."
+tags: ["sales","operations","analytics","strategy"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/roadmap-communicator/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: roadmap-communicator
-description: "Use when preparing roadmap narratives, release notes, changelogs, or stakeholder updates tailored for executives, engineering teams, and customers."
-tags: ["product","writing"]
+description: "Use when preparing roadmap presentations, stakeholder updates, release notes, changelogs or feature announcements for executives, engineers or customers. Covers Now/Next/Later, timeline and theme-based formats plus audience-specific update patterns."
+tags: ["product","writing","communication","documentation"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

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

@@ -1,7 +1,7 @@
 ---
 name: rust-engineer
-description: "Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option."
-tags: ["engineering","backend"]
+description: "Use when writing, reviewing or debugging Rust end to end: ownership and lifetimes, traits, thiserror error handling, async tokio, tests and clippy gates. Persona with reference files. For an idioms catalogue, use rust-patterns."
+tags: ["engineering","backend","rust","debug"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

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

@@ -1,7 +1,7 @@
 ---
 name: rust-patterns
-description: "Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications. Use when writing or reviewing Rust code and ownership, error handling, traits, or concurrency is in question."
-tags: ["engineering"]
+description: "Use when writing or reviewing Rust code and idiom is in question: ownership and borrowing, Result and ? error propagation, traits, concurrency and crate layout. A patterns catalogue with good vs bad examples; for an end-to-end build persona, use rust-engineer."
+tags: ["engineering","rust","coding-standards"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/safe-executor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: safe-executor
-description: "Safe Executor role best practices. Runs untrusted or agent-generated code without letting it touch the host, adjacent workloads, or secrets — the last line of defense when code execution itself is the feature."
-tags: ["security"]
+description: "Use when an org role acts as safe executor and must run untrusted or agent-generated code without touching the host, other workloads or secrets. Covers microVM or gVisor isolation, hard resource limits, default-deny network, per-run filesystems, no shell interpolation and ephemeral sandboxes."
+tags: ["security","agents","docker"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/sales-coach/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: sales-coach
-description: "Sales Coach role best practices. Improves rep performance through structured, ongoing coaching — call reviews, skill-building, and habit reinforcement — rather than one-off feedback or deal rescue."
-tags: ["sales"]
+description: "Use when an org role acts as sales coach and must improve rep performance through ongoing call reviews, skill-building and habit reinforcement. Covers weekly rubric-based review loops, one or two skills per session, GROW 1:1s, objection libraries and tracking behavior change. For discovery calls specifically, use discovery-coach."
+tags: ["sales","people","leadership"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/sales-enablement/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: sales-enablement
-description: "When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts."
-tags: ["sales","writing"]
+description: "Use when creating B2B sales collateral reps will actually use: pitch decks, one-pagers, objection-handling docs, demo scripts and battlecards. Gathers value prop, sales motion and current assets first. For finding prospects use sales-prospecting; for running demos as a role use sales-engineer."
+tags: ["sales","writing","content","competitive-analysis"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

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

@@ -1,7 +1,7 @@
 ---
 name: sales-engineer
-description: "Sales Engineer role best practices. Bridges product capability and customer need during the technical sales cycle — running discovery, demos, and POCs that prove a solution actually solves the buyer's problem, not just that it has features."
-tags: ["sales"]
+description: "Use when an org role acts as sales engineer and must run technical discovery, tailored demos and scoped POCs that prove the product fits the buyer. Covers discovery-to-demo mapping, POC scorecards, objection libraries and reference architectures. For making collateral, use sales-enablement."
+tags: ["sales","engineering","communication"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/sales-prospecting/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: sales-prospecting
-description: "When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses."
-tags: ["sales"]
+description: "Use when finding, qualifying and building a list of prospects to contact, for B2B SaaS, general B2B, local small businesses or first-customer demand signals. Branch-specific workflows from ICP definition to sourcing and qualification. For collateral, use sales-enablement."
+tags: ["sales","customer-research","growth"]
 tools: []
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/schema-markup/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: schema-markup
-description: "When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions \"schema markup,\" \"structured data,\" \"JSON-LD,\" \"rich snippets,\" \"schema.org,\" \"FAQ schema,\" \"product schema,\" \"review schema,\" \"breadcrumb schema,\" \"Google rich results,\" \"knowledge panel,\" \"star ratings in search,\" or \"add structured data.\""
-tags: ["marketing","frontend"]
+description: "Use when adding, fixing or optimizing schema.org structured data with JSON-LD for rich results: FAQ, product, review, article, organization and more. Covers accuracy, Google's guidelines and validation."
+tags: ["marketing","frontend","seo"]
 tools: ["monograph_query"]
 license: MIT
 source: https://github.com/coreyhaines31/marketingskills

package/org-skills/scientific-brainstorming/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: scientific-brainstorming
-description: "Facilitates evidence-aware scientific ideation with independent generation, structured discussion, explicit assumptions, transparent evaluation, adversarial review, and decision logs. Use for early-stage research brainstorming or prioritizing candidate directions; hand off empirical validation, study design, ethics or regulatory review, and clinical questions to appropriate experts or skills."
-tags: ["research","science"]
+description: "Use when generating and prioritizing early-stage research ideas, with independent ideation, explicit assumptions, adversarial review and decision logs. Outputs are proposals, not findings. For judging existing evidence use scientific-critical-thinking."
+tags: ["research","science","planning"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/scientific-critical-thinking/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: scientific-critical-thinking
-description: "Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws."
-tags: ["research","science"]
+description: "Use when judging the rigor of scientific claims or studies: design validity, bias and confounding, statistics, and GRADE or Cochrane risk of bias. For rubric-scored feedback on a paper or proposal, use scientific-thinking-scholar-evaluation."
+tags: ["research","science","evaluation","statistics"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/scientific-thinking-literature-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: scientific-thinking-literature-review
-description: "Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging. Use when the task is to find, screen, synthesize, and cite a body of academic or technical literature."
-tags: ["research","science"]
+description: "Use when finding, screening, synthesizing and citing a body of academic or technical literature as a narrative, scoping or systematic review or meta-analysis. Covers question framing with PICO, search planning, screening, citation checks and evidence logs."
+tags: ["research","science","writing"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/scientific-thinking-scholar-evaluation/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: scientific-thinking-scholar-evaluation
-description: "Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback. Use when evaluating academic or scientific work — papers, proposals, methods sections, or evidence quality — against a repeatable rubric."
-tags: ["research","science","writing"]
+description: "Use when evaluating a paper, proposal, thesis chapter or literature review with a repeatable 1-5 rubric on methods, evidence and citations. Supports comprehensive, targeted or comparative scope and revision feedback. For general claim appraisal, use scientific-critical-thinking."
+tags: ["research","science","writing","evaluation"]
 tools: []
 license: MIT
 source: https://github.com/affaan-m/ECC

package/org-skills/scientific-visualization/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: scientific-visualization
-description: "Create and audit truthful, accessible, publication-ready scientific figures with Matplotlib, Seaborn, or Plotly. Use for figure design, multi-panel layouts, uncertainty and missing-data displays, color/contrast review, image metadata validation, and journal export planning."
-tags: ["data","science","design"]
+description: "Use when creating or auditing publication-ready scientific figures in Matplotlib, Seaborn or Plotly: honest encodings, panels, uncertainty and color. Stresses data integrity, provenance and verifying live journal requirements."
+tags: ["data","science","design","visualization","python"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/scientific-writing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: scientific-writing
-description: "Draft, revise, and audit scientific manuscripts or reports with explicit evidence provenance, reporting-guideline coverage, authorship accountability, confidentiality controls, and local consistency checks. Use for manuscript sections, references, declarations, tables, figures, or submission preparation when scientific accuracy and traceability matter."
-tags: ["writing","science","research"]
+description: "Use when drafting, revising or auditing scientific manuscripts or reports with evidence provenance, reporting guidelines and authorship accountability. Enforces no fabricated citations or results and confidentiality controls. For figures use scientific-visualization."
+tags: ["writing","science","research","documentation"]
 tools: []
 license: MIT
 source: https://github.com/K-Dense-AI/scientific-agent-skills

package/org-skills/scout-explorer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: scout-explorer
-description: "Scout Explorer role best practices. Explores unfamiliar territory — a codebase, a dependency tree, an unknown system — and reports back concrete, actionable findings without acting on them itself."
-tags: ["operations"]
+description: "Org role guidance for a scout explorer: map an unfamiliar codebase, dependency tree or system and report triaged, located findings without fixing anything. Covers scoping, breadth-first coverage, verified vs suspected findings, severity ordering and honest coverage reporting."
+tags: ["operations","research","coordination"]
 tools: []
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/secrets-vault-manager/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: secrets-vault-manager
-description: "Use when the user asks to set up secret management infrastructure, integrate HashiCorp Vault, configure cloud secret stores (AWS Secrets Manager, Azure Key Vault, GCP Secret Manager), implement secret rotation, or audit secret access patterns."
-tags: ["security","devops"]
+description: "Use when setting up secret management infrastructure: HashiCorp Vault, AWS Secrets Manager, Azure Key Vault or GCP Secret Manager, rotation and access audits. Covers Vault auth methods and policies, dynamic secrets, Kubernetes and CI/CD secret injection and leak revocation. Not for local env-file hygiene."
+tags: ["security","devops","cloud","kubernetes"]
 tools: []
 license: MIT
 source: https://github.com/alirezarezvani/claude-skills

package/org-skills/secure-code-guardian/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: secure-code-guardian
-description: "Use when implementing authentication/authorization, securing user input, or preventing OWASP Top 10 vulnerabilities — including custom security implementations such as hashing passwords with bcrypt/argon2, sanitizing SQL queries with parameterized statements, configuring CORS/CSP headers, validating input with Zod, and setting up JWT tokens."
-tags: ["security","engineering"]
+description: "Use when implementing security controls in code: auth and authorization, password hashing, parameterized SQL, input validation, CORS and CSP headers, JWTs. Workflow of threat model, implement, validate against OWASP Top 10 with checkpoints, plus TypeScript examples (bcrypt, Zod, Helmet). Implementation-focused, not an audit."
+tags: ["security","engineering","typescript","api"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills

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

@@ -1,7 +1,7 @@
 ---
 name: security-architect
-description: "Security Architect role best practices. Designs security into systems before they're built — threat models, trust boundaries, zero-trust architecture, and authn/authz patterns — so vulnerabilities never get a chance to ship."
-tags: ["security"]
+description: "Use when an org role acts as security architect and must design security in before build: threat models, trust boundaries, zero-trust and authn/authz patterns. Covers STRIDE, least privilege, defense in depth, secrets architecture, OIDC and mTLS, and ADRs for security controls."
+tags: ["security","architecture","planning"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

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

@@ -1,7 +1,7 @@
 ---
 name: security-auditor
-description: "Security Auditor role best practices. Independently assesses existing code and systems for exploitable vulnerabilities, evidences findings with severity and remediation, and verifies fixes actually close the gap."
-tags: ["security"]
+description: "Use when an org role acts as security auditor and must assess existing code and systems for exploitable vulnerabilities, rate severity, and re-test fixes. Covers OWASP and CWE checklists, auth and IDOR testing, SAST/SCA/secrets scanning and scoped audits. For smart contracts, use blockchain-auditor."
+tags: ["security","audit","code-review"]
 tools: ["monograph_query","monograph_context","monograph_impact"]
 license: Apache-2.0
 source: https://github.com/monoes/monomind

package/org-skills/security-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: security-review
-description: "Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns."
-tags: ["security","engineering"]
+description: "Use when adding auth, user input, file uploads, secrets, API endpoints or payment features: a pass/fail security checklist with TypeScript patterns. Covers secrets in env vars, Zod validation, SQL injection, XSS, CSRF, rate limiting and data exposure. A developer checklist; for full audits and pentest reports use security-reviewer."
+tags: ["security","engineering","typescript","code-review"]
 tools: ["monograph_query","monograph_context"]
 license: MIT
 source: https://github.com/affaan-m/ECC

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

@@ -1,7 +1,7 @@
 ---
 name: security-reviewer
-description: "Identifies security vulnerabilities, generates structured audit reports with severity ratings, and provides actionable remediation guidance. Use when conducting security audits, reviewing code for vulnerabilities, or analyzing infrastructure security. Invoke for SAST scans, penetration testing, DevSecOps practices, cloud security reviews, dependency audits, secrets scanning, or compliance checks."
-tags: ["security","engineering"]
+description: "Use when conducting a security audit or pentest: SAST, dependency and secrets scans, manual auth and crypto review, and a severity-rated report. Tools include Semgrep, Bandit, Gitleaks, npm audit and Trivy, plus infrastructure and cloud checks; requires scoped authorization. For an in-flight coding checklist use security-review."
+tags: ["security","engineering","audit","code-review"]
 tools: ["monograph_query","monograph_context","monograph_impact","monograph_suggest"]
 license: MIT
 source: https://github.com/Jeffallan/claude-skills