Loading...
Loading...
Found 340 Skills
Use when academic research involves human subjects, public web data, platform scraping, sensitive domains, privacy risk, dataset sharing, consent, IRB, licenses, or data retention.
Use to codify sales rules of engagement, escalation paths, and exception workflows.
Define how a design system evolves — contribution models, versioning, change management, and deprecation.
Use to set cadences, decision logs, and escalation paths for enterprise pursuits.
Explain MotherDuck security, governance, and access-control patterns. Use when a security_compliance_owner, technical_owner, or application_builder is asking about residency, access boundaries, service accounts, isolation, sharing, or governance posture.
Add policy enforcement, zero-trust identity, and execution sandboxing to AI agents with Microsoft's Agent Governance Toolkit
Use to run pricing councils, track decisions, and enforce approval workflows.
Expert ISO 42001 AI Management System (AIMS) compliance advisor. Use this skill whenever a user asks about ISO/IEC 42001:2023, AI governance, AI management systems, AI risk assessment, AI system impact assessment, Annex A controls for AI, Statement of Applicability for AI systems, AI policy, responsible AI, AI lifecycle management, AI incident management, AI transparency, AI bias, AI certification readiness, or any topic related to implementing or auditing an AI Management System. Also trigger for questions like "how do I become ISO 42001 certified?", "what controls does ISO 42001 require?", "how do I assess AI risk under 42001?", "what is an AIMS?", or any request involving organisational governance of AI systems, responsible AI frameworks, or AI regulatory compliance aligned to an ISO standard.
Use to manage brand guidelines, approvals, and ongoing refresh cadence.
Unity Catalog governance patterns, permissions models, security best practices, and policy enforcement for enterprise data governance.
NEVER escalate without investigation first. This is the Iron Law. Use when evaluating whether to escalate models, facing genuine complexity requiring deeper reasoning, novel patterns with no existing solutions, high-stakes decisions requiring capability investment. Do not use when thrashing without investigation - investigate root cause first. DO NOT use when: time pressure alone - urgency doesn't change task complexity. DO NOT use when: "just to be safe" - assess actual complexity instead.
Design System Governance Workflow for auditing, refactoring, and syncing enterprise design systems, design tokens, Figma variables, and developer handoff outputs.