-21risk-automation
-21risk-automation
【开发与工程】Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
一个技能,一个新的可能。找到适合你的 AI 工作流。
-21risk-automation
【开发与工程】Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
dimensions
【开发与工程】Use when reviewing image assets, markup, and CDN or build transforms related to Set explicit width and height on images. Check encoded size, rendered size, loading strategy, and above-the-fold impact together. Separate real CLS risks from tiny decorative SVGs or ornament-only assets that are unlikely to move surrounding content.
stop-words
【效率与协作】Use when applies primarily when creating new content pages. Low priority for existing indexed pages where redirect risk outweighs gain. Use when building a slug naming convention.
iso-standards-readiness
【文档与办公】Prepares and structurally reviews readiness evidence for ISO management-system and laboratory-competence standards - ISO 13485 medical device QMS, ISO 14971 device risk management, ISO/IEC 17025 testing and calibration laboratories, and ISO 15189 medical laboratories. Use when organizing declared scope, controlled documents, risk-management files, sc…
scientific-critical-thinking
【设计与创意】Evaluates scientific claims and evidence quality. Applies to experimental design validity, biases and confounders, statistical interpretation, evidence grading frameworks (GRADE, Cochrane Risk of Bias), and teaching critical analysis. Supports evidence appraisal and identifying flaws; formal peer review writing belongs to peer-review.
scikit-survival
【效率与协作】Builds, evaluates, and audits right-censored or competing-risk survival workflows with scikit-survival, including leakage-safe preprocessing, model selection, probability prediction, and censoring-aware metrics.
ai-loop
【开发与工程】Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
ai-red-teaming
【数据与研究】Run structured AI red team exercises for jailbreak resistance, data exfiltration risk, harmful output controls, and agent tool abuse resilience.
architecture-review
【开发与工程】Review repository architecture using Ontoly Software Graph and MCP capabilities. Use when asked to explain architecture, module boundaries, package topology, service ownership, or architectural risk.
attack-tree-construction
【设计与创意】Build comprehensive attack trees to visualize threat paths. Use when mapping attack scenarios, identifying defense gaps, or communicating security risks to stakeholders.
audit-skills
【数据与研究】Expert security auditor for AI Skills and Bundles. Performs non-intrusive static analysis to identify malicious patterns, data leaks, system stability risks, and obfuscated payloads across Windows, macOS, Linux/Unix, and Mobile (Android/iOS).
before-you-build
【开发与工程】Review product risk before coding by checking demand, alternatives, channels, switching costs, and failure signals.
brooks-lint
【设计与创意】AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.
brooks-review
【设计与创意】PR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books.
brooks-sweep
【数据与研究】Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution.
brooks-test
【开发与工程】Review test-suite quality using established testing literature; identify brittleness, mock abuse, unclear fixtures, weak assertions, slow feedback, and maintenance risks.
cockney
【效率与协作】Cheeky Cockney coding mode: terse replies, the smallest correct change, plain English for anything risky.
comprehensive-review-pr-enhance
【文档与办公】Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.