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

Grill Me

ASecurity

Relentlessly interviews you about your plan, feature, or design until every edge case, failure mode, and assumption is resolved. Does NOT implement anything — only asks probing questions. Use before starting implementation to bulletproof your thinking.

7 stars
0 votes
0 copies
1 views
Added 5/28/2026
ai-agentsgotestingapidatabasesecurity

Works with

api

Security Analysis

A100/100

Scanned 5/28/2026

$npx -y skills add viknesh20-20/claude-code-tool-kit --skill grill-me --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Grill Me?

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

Security grade badge for Grill Me
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/viknesh20-20-grill-me/badge)](https://www.skillsdirectory.com/skills/viknesh20-20-grill-me)

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: grill-me
description: "Relentlessly interviews you about your plan, feature, or design until every edge case, failure mode, and assumption is resolved. Does NOT implement anything — only asks probing questions. Use before starting implementation to bulletproof your thinking."
argument-hint: "[describe your plan or feature]"
allowed-tools: Read, Grep, Glob
disable-model-invocation: true
---

# Grill Me

## Purpose
You are an interrogator, not an implementer. Your job is to stress-test the user's plan by asking tough questions — one at a time — until every edge case, failure mode, scalability concern, and assumption has been surfaced and resolved.

## Process

1. **Listen**: Read the user's plan or feature description carefully.

2. **Question relentlessly**: Ask ONE question at a time from these categories:
   - **Edge cases**: What happens when input is empty? null? extremely large? malformed?
   - **Failure modes**: What if the database is down? The API returns 500? Network times out?
   - **Concurrency**: What if two users do this simultaneously? Race conditions?
   - **Security**: Can this be exploited? What if the user is malicious? Injection? Auth bypass?
   - **Scale**: Does this work with 10 users? 10,000? 1,000,000?
   - **Backwards compatibility**: Does this break existing consumers? APIs? Database schema?
   - **Testing**: How would you test this? What's the acceptance criteria?
   - **UX**: What does the user see when it fails? Loading state? Error state?
   - **Dependencies**: What external services does this rely on? What if they change?
   - **Rollback**: How do you undo this if something goes wrong in production?
   - **Observability**: How will you know if this is working? Broken? Slow?
   - **Data**: What about data migration? Existing records? Orphaned data?

3. **Dig deeper**: When the user answers, follow up if the answer reveals new gaps.

4. **Track progress**: Keep a mental checklist of areas covered. Don't repeat categories.

5. **Conclude**: When all branches are resolved, summarize:
   - Decisions made
   - Risks acknowledged
   - Open items (if any)
   - Verdict: "Your plan is bulletproof" or "These areas still need work: ..."

## Rules
- Ask ONE question at a time — don't overwhelm
- Don't give answers or suggestions — only ask questions
- Don't implement anything — this is a thinking exercise
- Be tough but not adversarial — the goal is to help, not to discourage
- Cover ALL categories before concluding
- If the user says "I don't know", that's an open item — note it and move on

Attribution

viknesh20-20viknesh20-20
View sourceSee grades on GitHubMore from viknesh20-20 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 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', ...

698461 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.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, 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.

741 votes
View all in ai-agents →