分析
分析、报表与可视化
linking
florianbuetow
This skill should be used when the user asks to "check for linkability", "analyze cross-service tracking", "find privacy issues related to user correlation", "check for cross-domain tracking", or mentions "linkability" in a privacy context. Maps to LINDDUN category L.
Anomaly Detection
aj-geddes
Identify unusual patterns, outliers, and anomalies in data using statistical methods, isolation forests, and autoencoders for fraud detection and quality monitoring
quiz-generator
dmccreary
This skill generates interactive multiple-choice quizzes for each chapter of an intelligent textbook, with questions aligned to specific concepts from the learning graph and distributed across Bloom's Taxonomy cognitive levels to assess student understanding effectively. Use this skill after chapter content has been written and the learning graph exists.
learning-graph-generator
dmccreary
Generates a comprehensive learning graph from a course description, including 200 concepts with dependencies, taxonomy categorization, and quality validation reports. Use this when the user wants to create a structured knowledge graph for educational content.
glossary-generator
dmccreary
This skill automatically generates a comprehensive glossary of terms from a learning graph's concept list, ensuring each definition follows ISO 11179 metadata registry standards (precise, concise, distinct, non-circular, and free of business rules). Use this skill when creating a glossary for an intelligent textbook after the learning graph concept list has been finalized.
faq-generator
dmccreary
This skill generates a comprehensive set of Frequently Asked Questions (FAQs) from the course description, course content, learning graphs, concept lists, MicroSims, and glossary terms to help students understand common questions and prepare content for chatbot integration. Use this skill after course description, learning graph, glossary, and at least 30% of chapter content exist.
book-metrics-generator
dmccreary
This skill generates comprehensive metrics reports for intelligent textbooks built with MkDocs Material, analyzing chapters, concepts, glossary terms, FAQs, quiz questions, diagrams, equations, MicroSims, word counts, and links. Use this skill when working with an intelligent textbook project that needs quantitative analysis of its content, typically after significant content development or for project status reporting. The skill creates two markdown files - book-metrics.md with overall statistics and chapter-metrics.md with per-chapter breakdowns - in the docs/learning-graph/ directory.
investigate
TokenRollAI
"Use when user asks 'what is X', 'how does X work', 'find out about', 'analyze', 'explain the code', or needs quick codebase investigation. Returns findings directly in conversation without saving files. Prefer this over Explore agent."
workflow-results
SergeiNikolenko
"Use when accepting and displaying externally produced protein prep, ligand prep, docking, MD, cleanup, or bulk property artifacts."
visual-qa
SergeiNikolenko
"Use when visually verifying Burette Browser preview or desktop app state without replacing typed observe/action contracts."
grace-plan
osovv
"Run the GRACE architectural planning phase. Use when you have requirements and technology decisions defined and need to design the module architecture, create contracts, and build the knowledge graph. Produces development-plan.xml and knowledge-graph.xml."
grace-status
osovv
"Show the current health status of a GRACE project. Use to get an overview of project artifacts, codebase metrics, knowledge graph health, and suggested next actions — helps identify drift, missing contracts, or unpaired semantic blocks."
grace-refresh
osovv
"Synchronize the GRACE knowledge graph with the actual codebase. Use after manual code changes, refactoring, or when you suspect drift between the knowledge graph and the code — scans all source files, detects missing/orphaned modules and stale CrossLinks, and proposes fixes."
grace-add
osovv
"Add a new module to a GRACE project with contract and knowledge graph entry. Use when you need to introduce a new module that wasn't part of the original plan — designs the contract, updates planning artifacts, generates code, and verifies integration."
2d-or-3d-force-graph-with-lit
rodydavis
Learn how to create interactive 2D and 3D force graphs using Lit, a lightweight web component library, with this step-by-step tutorial.
inertia-rails-controllers
inertia-rails
ALWAYS render inertia: { key: data } to pass data as props — instance variables are NOT auto-passed (only alba-inertia does that). Rails controller patterns for Inertia.js: render inertia, prop types (defer, optional, merge, scroll), shared data, flash, PRG redirects, validation errors. Use when writing controllers that load data, display records, or serve Inertia responses. CRITICAL: external URLs (Stripe/OAuth) MUST use inertia_location, NEVER redirect_to.
dart-architecture
dartsim
"DART Architecture: the DART 7 multi-physics, multi-solver, multi-backend simulation pipeline and where each abstraction is owned"
dart-architecture
dartsim
"DART Architecture: the DART 7 multi-physics, multi-solver, multi-backend simulation pipeline and where each abstraction is owned"
grace-ask
osovv
"Answer a question about a GRACE project using full project context. Use when the user has a question about the codebase, architecture, modules, or implementation — loads all GRACE artifacts, navigates the knowledge graph, and provides a grounded answer with citations."
grace-generate
osovv
"Generate code for a specific GRACE module with full semantic markup. Use when a module has been planned and contracted in development-plan.xml and you need to generate the actual implementation code with MODULE_CONTRACT, MODULE_MAP, semantic blocks, and knowledge graph updates."
grace-reviewer
osovv
"GRACE integrity reviewer. Use when validating semantic markup correctness, contract completeness, knowledge graph consistency, or after code changes to ensure GRACE conventions are maintained."
grace-execute
osovv
"Execute the full GRACE development plan step by step, generating code for each pending module with validation and commits. Use when the architecture is planned and you want to generate all modules sequentially with review checkpoints."
plain-install
dropseed
Installs Plain packages and guides through setup steps. Use when adding new packages to a project.
plain-bug
dropseed
Submit a bug report for the Plain framework. Use when you encounter a bug, error, or unexpected behavior. Collects context and creates a GitHub issue.