Agent skill

Decision Questionnaire

by Luciole-Studio in Luciole-Studio/Misaka-Agent

Turn an unanswerable decision into a questionnaire doc. An agent skill from Luciole-Studio/Misaka-Agent.

MITAuto-check passedBackend & APIs

Install Decision Questionnaire

skills CLI
$ npx skills add Luciole-Studio/Misaka-Agent --skill decision-questionnaire -a claude-code

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

GitHub CLI
$ gh skill install Luciole-Studio/Misaka-Agent decision-questionnaire --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/Luciole-Studio/Misaka-Agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/misaka/core/skills/assets/optional/productivity/decision-questionnaire .claude/skills/decision-questionnaire && 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
decision-questionnaire
GitHub stars
158
Used in
1 other repo
Token cost
~1k tokens
SKILL.md length
455 words
Files
1
Skills in repo
77
Repo updated
First seen
Licence
MIT

At a glance

Turn an unanswerable decision into a questionnaire doc. An agent skill from Luciole-Studio/Misaka-Agent.

  • Works in 2 steps: Who is it going to? Role, expertise,… → What do you need back? The specific…
  • Backend & APIs work in your project
  • SKILL.md covers When to Use, Core Principle: Interview the…, Document Structure and Pitfalls, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Decision Questionnaire is an agent skill from Luciole-Studio/Misaka-Agent. Turn an unanswerable decision into a questionnaire doc.

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

It sits in Backend & APIs. The repository describes itself as: A multi-agent research system for the humanities and social sciences. The licence is MIT.

When your agent uses it

  • Backend & APIs work in your project

Example prompts

  • “/decision-questionnaire”

Workflow steps

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

  1. Who is it going to? Role, expertise, relationship to the user. This
  2. What do you need back? The specific decisions or facts the user

What it can do on your machine

Read from SKILL.md and the folder at commit 3bcf7a3. 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 (its code samples are markdown).

    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

Decision Questionnaire loads about 1k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 455 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~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 Luciole-Studio/Misaka-Agent at commit 3bcf7a3, republished under its MIT licence (© Luciole-Studio). 455 words, ~1,041 tokens.

Download SKILL.mdSave it as .claude/skills/decision-questionnaire/SKILL.md (or your agent's skills folder).
name
decision-questionnaire
description
Turn an unanswerable decision into a questionnaire doc.
version
1.0.0
author
Matt Pocock (mattpocock/skills, to-questionnaire) + Hermes Agent
license
MIT
platforms
linux, macos, windows

Decision Questionnaire

Turns something the user can't answer alone into a questionnaire: a Markdown document they hand to one person to fill in async, or fill out together in a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them.

Ported from mattpocock/skills' MIT-licensed to-questionnaire skill.

When to Use

  • A decision blocks on facts or judgment held by someone else (a domain expert, a stakeholder, a vendor contact, ops)
  • The user says "I need to ask X about this" or keeps deferring a decision pending someone else's input
  • Preparing for a meeting where specific answers must come back

Do NOT use when the answer is discoverable from the environment (codebase, docs, web) — find it yourself first.

Core Principle: Interview the Send, Not the Subject

The user cannot answer the subject-matter questions (that's the point), but they can ALWAYS answer questions about the send. Interview them only about that, in two short exchanges:

  1. Who is it going to? Role, expertise, relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user doesn't.
  2. What do you need back? The specific decisions or facts the user can't resolve alone. Done when you have a concrete list of what the user must walk away able to do or decide.

Then write the questionnaire: draft questions aimed at the gap between what the recipient knows and what the user needs, following the structure below. Write it to decision-questionnaire-<slug>.md in the current directory (slug from the topic) and report the absolute path. Done when the file exists and every item from step 2 is covered by a question.

Show full SKILL.md (166 more words)Show less

Document Structure

Frame it as a discovery questionnaire: the user lacks context, the recipient holds it. Order questions most-important-first (async means you may only get one pass). Group under ## headings by theme once there are more than a handful.

Template:

markdown
# <Questionnaire title>

**Purpose:** why this questionnaire exists and the decision riding on it.

**From:** <the user> · **To:** <the recipient> ·
**How your answers will be used:** <where they go>

## Context

One paragraph orienting a recipient who wasn't in the user's head. Enough
to answer well, not a page.

## How to answer

Deadline and rough effort. Partial answers and "I don't know" are useful:
flag anything you're unsure of rather than skipping it.

## <Theme heading>

### <One question — a single idea, never compound>

_Why this matters: <one line, only where the question could be misread or
invite a throwaway answer>._

>

## Anything else?

A closing catch-all: anything we didn't ask that we should know?

Every question gets an answer stub (>) directly beneath it.

Pitfalls

  1. Grilling the user about the subject. They can't answer it — that's why the document exists. Only interview the send.
  2. Compound questions. One idea per question; split "and/or" questions.
  3. Burying the critical question. Most-important-first; async recipients fade.
  4. Context dump. One orienting paragraph, not the whole history.
  5. Skipping the "why this matters" line on ambiguous questions. It's what turns a throwaway answer into a useful one — but don't add it to questions that are already unambiguous.

Verification

  • Recipient's role/knowledge and the needed outcomes captured in two exchanges before drafting
  • Every step-2 item covered by at least one question
  • Questions single-idea, most-important-first, answer stubs present
  • File written and absolute path reported to the user

© Luciole-Studio, 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 misaka/core/skills/assets/optional/productivity/decision-questionnaire of Luciole-Studio/Misaka-Agent.

Open the folder on GitHubat commit 3bcf7a3

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Luciole-Studio/Misaka-Agent, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Decision Questionnaire 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.

Decision Questionnaire compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Decision Questionnaire this skillLuciole-Studio/Misaka-Agent1581 repos~1kAutomated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Nestjs Best Practicesrolling-scopes/rsschool-app10k6 repos~1.2kAutomated safety check: PassMIT
Sub2API AdminWei-Shaw/sub2api44k1 repos~717Automated safety check: PassLGPL-3.0
Firecrawl Build Onboardingfirecrawl/firecrawl190k1 repos~1.4kAutomated safety check: NotesISC
Obsidian BasesAtmosphere/atmosphere3.8k22 repos~3.2kAutomated safety check: PassApache-2.0

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed
  • Nestjs Best Practices

    rolling-scopes/rsschool-app

    NestJS best practices and architecture patterns for building production-ready applications.

    10k GitHub starsUsed in 6 repos~1.2k tokens
    Backend & APIsAuto-check passed
  • Sub2API Admin

    Wei-Shaw/sub2api

    Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.

    44k GitHub starsUsed in 1 repo~717 tokens
    Backend & APIsAuto-check passed
  • Firecrawl Build Onboarding

    firecrawl/firecrawl

    Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

    190k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check: notes
  • Obsidian Bases

    Atmosphere/atmosphere

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.

    3.8k GitHub starsUsed in 22 repos~3.2k tokens
    Backend & APIsAuto-check passed
  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed

More from Luciole-Studio/Misaka-Agent

All 77 skills in this repo
  • Kanban Video Orchestrator

    Luciole-Studio/Misaka-Agent

    Plan and run multi-agent video production pipelines. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check: notes
  • Ast Grep

    Luciole-Studio/Misaka-Agent

    AST-aware structural code search and rewrite via ast-grep. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~3.2k tokens
    Auto-check passed
  • Drug Discovery

    Luciole-Studio/Misaka-Agent

    Drug discovery: ChEMBL search, drug-likeness, interactions. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~2.2k tokens
    Auto-check passed
  • Fitness Nutrition

    Luciole-Studio/Misaka-Agent

    Workout planning, macros, and body metrics via wger/USDA. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check passed
  • Hyperframes

    Luciole-Studio/Misaka-Agent

    Render MP4/WebM videos from HTML compositions. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Osint Investigation

    Luciole-Studio/Misaka-Agent

    Follow the money via public records and sanctions data. An agent skill from Luciole-Studio/Misaka-Agent.

    158 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed

Categories

Questions about Decision Questionnaire

What does Decision Questionnaire do?

Turn an unanswerable decision into a questionnaire doc. An agent skill from Luciole-Studio/Misaka-Agent. Decision Questionnaire is an agent skill from Luciole-Studio/Misaka-Agent. Turn an unanswerable decision into a questionnaire doc.

When should I use Decision Questionnaire?

Decision Questionnaire fits situations like: backend & APIs work in your project.

How do I install Decision Questionnaire in Claude Code?

Run `npx skills add Luciole-Studio/Misaka-Agent --skill decision-questionnaire -a claude-code`. Or copy the skill folder (misaka/core/skills/assets/optional/productivity/decision-questionnaire in Luciole-Studio/Misaka-Agent) into .claude/skills/decision-questionnaire in your project. Claude Code loads it when a task matches its description.

How do I install Decision Questionnaire in Codex?

Run `npx skills add Luciole-Studio/Misaka-Agent --skill decision-questionnaire -a codex`. Or copy the skill folder (misaka/core/skills/assets/optional/productivity/decision-questionnaire in Luciole-Studio/Misaka-Agent) into .agents/skills/decision-questionnaire in your project. Codex loads it when a task matches its description.

Can I use Decision Questionnaire 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 Luciole-Studio/Misaka-Agent --skill decision-questionnaire -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/decision-questionnaire, .gemini/skills/decision-questionnaire, .github/skills/decision-questionnaire and .opencode/skills/decision-questionnaire in your project.

What does Decision Questionnaire need to run?

SKILL.md names no scripts, command-line tools or credentials: Decision Questionnaire is instructions for the agent only.

Does Decision Questionnaire 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 Decision Questionnaire 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 Decision Questionnaire use?

Decision Questionnaire 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 Decision Questionnaire use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Decision Questionnaire?

Skills that share tags, products or a category with Decision Questionnaire: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 44k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 190k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Decision Questionnaire?

Luciole-Studio (a GitHub organization) maintains it in Luciole-Studio/Misaka-Agent, which has 158 GitHub stars. The repository holds 77 skills in this directory. The repository was last updated on October 8, 2026.

Source: Luciole-Studio/Misaka-Agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.