Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Ai Use Case Intake

ASecurity

Intake a proposed AI use case and risk-classify it (EU AI Act tier / NIST AI RMF context), then gate it with the controls and documentation required before it can proceed. Use for AI governance intake, an AI use-case review board, or deciding what rigor a new AI project needs.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgotestingsecuritydocumentation

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add jassics/awesome-claude-security --skill ai-use-case-intake --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ai Use Case Intake?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Ai Use Case Intake
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jassics-ai-use-case-intake/badge)](https://www.skillsdirectory.com/skills/jassics-ai-use-case-intake)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: ai-use-case-intake
description: >-
  Intake a proposed AI use case and risk-classify it (EU AI Act tier / NIST AI RMF
  context), then gate it with the controls and documentation required before it can
  proceed. Use for AI governance intake, an AI use-case review board, or deciding
  what rigor a new AI project needs.
---

# Goal

A governance decision record for a proposed AI use case: its risk classification,
the obligations that follow, the required controls/evidence, and a clear
proceed / proceed-with-conditions / do-not-proceed outcome.

# Steps

1. **Capture the use case** — purpose, users and affected people, data used,
   autonomy/impact on decisions, deployment context, and vendor/build status.
2. **Classify risk:**
   - **EU AI Act tier** — unacceptable (prohibited) / high-risk / limited
     (transparency) / minimal. High-risk and prohibited categories drive most
     obligations; check whether the use case falls in a listed high-risk area.
   - **NIST AI RMF context** — characterize impact, stakeholders, and harm
     potential (reuse `ai-safety:harm-modeling`).
3. **Derive obligations** from the tier: required documentation (model/data cards,
   intended-use + limitations), human oversight, transparency/disclosure, data
   governance, testing/eval evidence, logging, and post-market monitoring.
4. **Map required controls to evidence** — which already exist vs. gaps. Pull from
   `ai-safety:safety-evaluation`, `bias-fairness-assessment`, `guardrail-review`,
   `responsible-ai-assessment`.
5. **Decide & record** — proceed / conditions / stop, with owner, conditions, and
   review date. Add to the AI inventory/register.

# Output

An intake decision record: use case · risk tier · obligations · required controls ·
evidence status · decision · conditions · owner · review date. Use
`security-reporting` for the record and an executive summary; this also feeds the
org's AI inventory.

# Notes

Classify the risk tier first — it sets how much rigor everything else needs, and it
catches prohibited uses before effort is spent. Keep the register current; intake
is the front door of the governance program, not a one-time form. Verify current EU
AI Act / NIST AI RMF text and any sector rules.

Attribution

jassicsjassics
View sourceSee grades on GitHubMore from jassics →
SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

696561 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes
View all in ai-agents →