Sets up the Polyspace Agentic Toolkit for any supported AI agent. Use when the user asks to "set up Polyspace", "set up the Polyspace Agentic Toolkit", "install the Polyspace MCP Server", "configure Polyspace for my agent", or wants to get Polyspace working with their AI application.
REQUIRED before searching for any Polyspace option documentation page. Use when the user asks about a Polyspace option (-c, -target, -sources, -boolean-types, -misra3, etc.), wants to find an option's doc page, or asks 'what does this option do'. This skill contains the only reliable method to locate option reference…
Adds Polyspace justification annotations to C/C++ source code. Use when the user asks to "justify this finding", "add a Polyspace annotation", "mark as false positive", "suppress finding", or wants to add justification comments to Polyspace findings.
Run an AI impact assessment — structured intake, risk analysis, UK regulatory classification (UK GDPR / DPA 2018, ICO AI guidance, sector-specific UK regulation), EU AI Act analysis where EU nexus exists, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed…
Run the cold-start interview — learns your UK AI governance practice and writes /.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/CLAUDE.md from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains [PLACEHOLDER] markers, or when…
Post-completion M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initialises from whatever deal artefacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A…
Export Giskard scan results into Collibra AI Governance. Use this whenever the user asks to export, push, sync, or import a Giskard scan, agent, or project (e.g. "Zephyr") into Collibra, or to update Collibra AI Governance assets, monitors, or Quality-tab metrics from Giskard. Also use it when the user asks to…
Generates tailored giskard.checks evaluation suites for RAG (Retrieval-Augmented Generation) systems. Use whenever a user describes a Q&A bot grounded in documents, a knowledge-base chatbot, a retrieval system, or wants to evaluate answer groundedness, faithfulness, hallucination, retrieval quality, citation accuracy…
Generates tailored giskard.checks test scenarios and suites for AI agents. Use when user describes their agent and fears, asks to "create scenarios", "test my agent", "generate checks", "evaluate my chatbot", "red-team my AI", or wants to build adversarial test cases for LLM-based applications.
Configures a harness. A Gemini CLI meta-framework for designing specialized subagent teams and collaboration skills. This skill MUST be invoked first when: (1) requests such as 'set up a harness', 'build/design/engineer a harness', (2) building an automation system for a new domain/project, (3) reconfiguring or…
Focused, on-demand project improver for active development. Option 0 scores the project or folder with a 0–100 health overview (Architecture, Maintainability, Performance, Security, Documentation), report-only. Options 1–7 improve ONE dimension at a time — performance (1), UI/UX (2), tidy/file order + comment hygiene…
Analyzes the architecture of any software project — web, mobile, browser extension, or npm package/library, in any JS/TS stack (Next.js, Astro, React Native, Expo, Lynx JS, Vite, etc.) or other languages if needed — and produces a folder of focused Markdown files covering architecture and packages/dependencies. Use…
Use this skill when working with Elasticsearch in any capacity — designing index mappings, writing or optimizing queries (Query DSL, ES|QL, KQL), planning cluster architecture, configuring ingest pipelines, tuning performance, troubleshooting cluster health, implementing search features, or building AI-powered search…
Use when the task is to create or update an ARCHITECTURE.md document that explains system structure, key modules, data flow, and major technical decisions. Do not use for lightweight README edits or changelog work.
Use when the task is to write or update the Features section in a README.md file based on existing code, docs, release notes, or user-provided changes. Do not use for general code changes unrelated to README content.
Use when the task is to apply SwiftUI formatting conventions, MARK comment organization, modifier-chain readability, preview style, or safe editing/improvement/optimization of existing Swift code logic. Do not use for broad repository architecture, platform targeting, build/test commands, folder layout policy, or…
1 1mo agoA73 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: