New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Interview Style Doc Building

by sickn33 in sickn33/agentic-awesome-skills

Build structured strategy documents by asking one question at a time and patching the file.

MITAuto-check passed

Install Interview Style Doc Building

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill interview-style-doc-building -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills interview-style-doc-building --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/interview-style-doc-building .claude/skills/interview-style-doc-building && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
interview-style-doc-building
GitHub stars
47k
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
588 words
Files
1
Skills in repo
1,493
Repo updated
First seen
Licence
MIT

At a glance

Build structured strategy documents by asking one question at a time and patching the file.

  • Works in 6 steps: Create the file with a skeleton (header,… → Ask ONE question. Concise. Specific.… → Wait for the answer. Don't ask the next… → …
  • SKILL.md covers When to Use, The Loop, Hard Rules and Question Design, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Interview Style Doc Building is an agent skill from sickn33/agentic-awesome-skills. Build structured strategy documents by asking one question at a time and patching the file.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

Example prompts

  • “/interview-style-doc-building”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Create the file with a skeleton (header, sections, "to be filled in" placeholders). Single write_file for the new file. After this, NEVER…
  2. Ask ONE question. Concise. Specific. Single-faceted. Open-ended where possible.
  3. Wait for the answer. Don't ask the next question yet.
  4. Patch the file with the user's answer in the correct section.
  5. Re-ask — next question, or follow-up if the answer was incomplete.
  6. Repeat until the file is complete.

What it can do on your machine

Read from SKILL.md and the folder at commit 680176d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Interview Style Doc Building loads about 1.1k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 588 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 680176d, republished under its MIT licence (© sickn33). 588 words, ~1,144 tokens.

Download SKILL.mdSave it as .claude/skills/interview-style-doc-building/SKILL.md (or your agent's skills folder).
name
interview-style-doc-building
description
Build structured strategy documents by asking one question at a time and patching the file.
category
productivity
risk
critical
source
community
source_repo
davidondrej/skills
source_type
community
date_added
2026-07-07
author
davidondrej
tags
documentation, interview, planning
tools
claude, codex
license
MIT

Interview-Style Doc Building

The user's preferred mode for creating durable strategic docs. AI does NOT propose content — AI asks one question, the user answers, AI patches the file, AI asks the next question. The file IS the conversation's output, updated incrementally.

When to Use

  • Building a new SSOT file (life priorities, life vision, principles, frameworks, ranked lists).
  • Filling out a structured doc the user explicitly wants to author themselves.
  • Quarterly/annual reviews where the user's words go into the file.

NOT for: day planning (use day-plan), task triage (organize-tasks), or anything where AI proposes content first.

The Loop

  1. Create the file with a skeleton (header, sections, "to be filled in" placeholders). Single write_file for the new file. After this, NEVER overwrite — only patch.
  2. Ask ONE question. Concise. Specific. Single-faceted. Open-ended where possible.
  3. Wait for the answer. Don't ask the next question yet.
  4. Patch the file with the user's answer in the correct section.
  5. Re-ask — next question, or follow-up if the answer was incomplete.
  6. Repeat until the file is complete.

Hard Rules

  • One question at a time. Never dump multiple questions in a single message. The user has flagged this.
  • Patch, don't overwrite. After the initial skeleton, use patch for every update. Never write_file to an existing doc.
  • Update the file BEFORE asking the next question. Order: receive answer → patch file → ask next question. Not the reverse.
  • Lists from the user are UNORDERED SETS. When the user lists items in response to "which X should we cover?" or "what are the Ys?", that is a SET, not a ranking. Never infer rank, priority, or sequence from the order they typed them. If you need ordering, ask explicitly: "Which of these is #1?"
  • Ask dynamics, not names. When the user references a person, don't ask "who is X?" — ask about the role/dynamic.
  • No snark, no attitude, no filler. Concise questions, concise acknowledgments.
  • No speculative additions. Don't invent sections, edge cases, or "anything else?" prompts unless the user asks.
Show full SKILL.md (257 more words)Show less

Question Design

  • Domain-discovery, not confirmation. "What wins against everything else?" — not "Is Business #1?"
  • Surface new reality. Each question should pull out info AI doesn't already have.
  • Engine-move framing where applicable. "What's the thing that, if true, makes the rest obvious?"
  • Concrete over abstract. "What's #2 — the domain that wins against everything except #1?" beats "Tell me about your second priority."

File Patching Pattern

After each answer:

  1. Read the relevant section (if not already in context).
  2. patch with old_string = placeholder or previous entry, new_string = updated content with the user's words preserved.
  3. Confirm the diff. Move on.

For ranked lists, append one rank at a time:

1. **Business** — Q2 #1 goal: ...
2. **Health** — get below 81.0 kg, sleep 9h/day, ...

Each rank gets patched in as the user confirms it.

Common Pitfalls

  • Assuming order from a set. The user lists "A, B, C, D" → AI writes "1. A, 2. B, 3. C, 4. D" → the user flags it. ALWAYS confirm rank explicitly.
  • Asking too many questions at once. Even bundling 2 violates the rule.
  • Overwriting the file instead of patching specific sections — destroys prior content.
  • Adding AI-generated content to fill out sections. Sections stay empty until the user provides the content.
  • Skipping the file update between Q&A pairs — the doc falls out of sync.

Pairing with Other Skills

  • day-plan — different pattern (task triage), not interview-style.
  • organize-tasks — Todoist-specific.
  • memory-management — separate from this; persona/preferences go to memory.

Limitations

  • Adapted from davidondrej/skills; verify local paths, tools, credentials, and agent features before acting.
  • For commands, remote access, scheduling, browser automation, or file-changing workflows, get explicit user approval and confirm the target environment first.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/interview-style-doc-building of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 680176d

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Interview Style Doc Building next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Interview Style Doc Building compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Interview Style Doc Building this skillsickn33/agentic-awesome-skills47k1 repos~1.1kAutomated safety check: PassMIT
Ask The Docssupabase/supabase111k—~2.4kAutomated safety check: PassApache-2.0
Interview Meaddyosmani/agent-skills103k6 repos~3.8kAutomated safety check: PassMIT
Interviewcodewhale-hq/Codewhale41k—~232Automated safety check: PassMIT
Ask User QuestionMemTensor/MemOS12k—~1kAutomated safety check: PassApache-2.0
Update Docsvercel/next.js143k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Ask The Docs

    supabase/supabase

    Official

    Answer questions about the Supabase docs app (apps/docs) using documented architecture, build pipeline, and review-pattern notes, and apply feature-design principles (codebase reuse, coding…

    111k GitHub stars~2.4k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    103k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed

  • Interview

    codewhale-hq/Codewhale

    Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec.

    41k GitHub stars~232 tokensUpdated today
    Auto-check passed

  • Ask User Question

    MemTensor/MemOS

    Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.

    12k GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Update Docs

    vercel/next.js

    Official

    This skill should be used when the user asks to "update documentation for my changes", "check docs for this PR", "what docs need updating", "sync docs with code", "scaffold docs for this feature"…

    143k GitHub stars~1.9k tokensUpdated today
    Documents & OfficeAuto-check passed

  • Interview Question Bank

    mohitagw15856/pm-claude-skills

    Build a structured, role-specific interview question bank with what good answers look like.

    1.4k GitHub stars~993 tokensUpdated yesterday
    Business, Finance & HRAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,493 skills in this repo

  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed

  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed

  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Interview Style Doc Building

What does Interview Style Doc Building do?

Build structured strategy documents by asking one question at a time and patching the file. Interview Style Doc Building is an agent skill from sickn33/agentic-awesome-skills. Build structured strategy documents by asking one question at a time and patching the file.

How do I install Interview Style Doc Building in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill interview-style-doc-building -a claude-code`. Or copy the skill folder (skills/interview-style-doc-building in sickn33/agentic-awesome-skills) into .claude/skills/interview-style-doc-building in your project. Claude Code loads it when a task matches its description.

How do I install Interview Style Doc Building in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill interview-style-doc-building -a codex`. Or copy the skill folder (skills/interview-style-doc-building in sickn33/agentic-awesome-skills) into .agents/skills/interview-style-doc-building in your project. Codex loads it when a task matches its description.

Can I use Interview Style Doc Building in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill interview-style-doc-building -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/interview-style-doc-building, .gemini/skills/interview-style-doc-building, .github/skills/interview-style-doc-building and .opencode/skills/interview-style-doc-building in your project.

What does Interview Style Doc Building need to run?

SKILL.md names no scripts, command-line tools or credentials: Interview Style Doc Building is instructions for the agent only.

Does Interview Style Doc Building access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Interview Style Doc Building safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Interview Style Doc Building use?

Interview Style Doc Building is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Interview Style Doc Building use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Interview Style Doc Building?

Skills that share tags, products or a category with Interview Style Doc Building: Ask The Docs (supabase/supabase, 111k stars), Interview Me (addyosmani/agent-skills, 103k stars), Interview (codewhale-hq/Codewhale, 41k stars) and Ask User Question (MemTensor/MemOS, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Interview Style Doc Building?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,379 GitHub stars. The repository holds 1,493 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.