gitlab-mcp: Skill for Claude Code

.github/skills/deep-interview/SKILL.md

deep-interview is a skill for Claude Code from kirti12025/gitlab-mcp. It costs 57 tokens per session (713 once invoked), scanned A, a copy of deep-interview, MIT.

A question-led process for turning a vague request into a precise specification. It repeatedly asks targeted questions and checks how much uncertainty remains.

In plain words
What is it for?
Clarifying broad ideas, gathering requirements for complex work, and preparing a well-defined task for later planning and execution.
Why use it?
It helps expose missing requirements and hidden assumptions before implementation begins.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is kirti12025/gitlab-mcp's own configuration. It tells Claude Code how to work on gitlab-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gitlab-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kirti12025/gitlab-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/kirti12025/gitlab-mcp/custom-tool-pipeline-summary/.github/skills/deep-interview/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/kirti12025/gitlab-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for deep-interview

README.md
[![agentmods](https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/deep-interview/github.svg)](https://agentmods.dev/skills/kirti12025/gitlab-mcp/deep-interview)
Your own site
<a href="https://agentmods.dev/skills/kirti12025/gitlab-mcp/deep-interview"><img src="https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/deep-interview/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for deep-interview

Your own site · 80×15
<a href="https://agentmods.dev/skills/kirti12025/gitlab-mcp/deep-interview"><img src="https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/deep-interview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 713 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00713
Opus 5.5 $0.00023 $0.00285
Sonnet 5.5 $0.00011 $0.00143
Haiku 4.5 $0.00006 $0.00071

Measured 2mo ago against content hash 16daa80ebb49, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

deep-interview scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to deep-interview — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/deep-interview/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deep Interview

Ouroboros-inspired Socratic questioning with mathematical ambiguity scoring. Replaces vague ideas with crystal-clear specifications by asking targeted questions that expose hidden assumptions.

Pipeline

deep-interview → ralplan (consensus refinement) → omg-autopilot (execution)

When to Use

  • User has a vague idea and wants thorough requirements gathering
  • Task is complex enough that jumping to code would waste cycles
  • User wants mathematically-validated clarity before execution

When NOT to Use

  • Detailed specific request with file paths → execute directly
  • Quick fix → delegate to @executor or /ralph
  • User says "just do it" → respect their intent

Phases

Phase 1: Initialize

  1. Parse the user's idea
  2. Detect brownfield vs greenfield (use @explore to check codebase)
  3. For brownfield: map relevant codebase areas
  4. Initialize ambiguity score at 100%

Phase 2: Interview Loop

Repeat until ambiguity <= 20% or user exits early:

  1. Generate question targeting the WEAKEST clarity dimension
  2. Ask ONE question at a time with current ambiguity context
  3. Score ambiguity across dimensions:
    • Goal Clarity (40% weight for greenfield, 35% brownfield)
    • Constraint Clarity (30% / 25%)
    • Success Criteria (30% / 25%)
    • Context Clarity (N/A / 15% for brownfield)
  4. Report progress with dimension scores and gaps
  5. Track ontology (key entities, stability ratio)

Phase 3: Challenge Agents

  • Round 4+: Contrarian - challenge core assumptions
  • Round 6+: Simplifier - probe for complexity removal
  • Round 8+: Ontologist - find the essence (if ambiguity > 30%)

Phase 4: Crystallize Spec

When ambiguity <= threshold, generate spec to .omc/specs/deep-interview-{slug}.md:

  • Goal, Constraints, Non-Goals, Acceptance Criteria
  • Assumptions Exposed & Resolved
  • Ontology (Key Entities) with convergence tracking
  • Interview Transcript

Phase 5: Execution Bridge

Present options:

  1. Ralplan → OMG Autopilot (Recommended): consensus-refine then execute
  2. Execute with omg-autopilot (skip ralplan)
  3. Execute with ralph: persistence loop
  4. Execute with team: parallel agents
  5. Refine further: continue interviewing

Read the full file on GitHub · 76 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 76 lines · 57 tokens per session scan A 16daa80ebb49

Subscribe to this mod's changes

deep-interview is a skill published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 713 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to deep-interview, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens