skill-interviewer

Guide interviews to scope new Antigravity skills and draft specifications.

8|3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ydnikolaev/antigravity-factory --skill skill-interviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-interviewer
Source: https://github.com/ydnikolaev/antigravity-factory/tree/main/.agent/skills/skill-interviewer
Command: npx skills add https://github.com/ydnikolaev/antigravity-factory --skill skill-interviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Skill Interviewer acts as a collaborative ideation partner that helps teams explore, scope, and articulate new Antigravity skills. It leads interviews, surfaces boundaries, and writes the initial Skill Specification for the eventual creator, without producing SKILL.md files itself.

Core Features & Use Cases

  • Ideation facilitation: Guides conversations to identify a skill's problem, triggers, inputs, and outputs.
  • Boundary definition: Clearly specifies what the skill DOES and DOES NOT do to prevent scope creep.
  • Spec writing: Produces a ready-to-hand-off Skill Specification artifact for the @skill-creator.
  • Ecosystem alignment: References existing TEAM.md, PIPELINE.md, and current skills to ensure alignment with the factory.

Quick Start

Activate the Interviewer when you have an idea for a skill. Start with prompts like "I have an idea for a skill" and let it ask clarifying questions, propose boundaries, and draft a formal specification. When ready, hand off to @skill-creator with the draft spec.

Frequently Asked Questions about skill-interviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a skill specification when I only have a rough idea?

Skill specification writing starts with a guided interview that explores your idea, identifies triggers and inputs, defines boundaries, and produces a ready-to-handoff spec document.

What is the best way to define boundaries for a new skill to prevent scope creep?

Boundary definition uses guided ideation interviews to clearly specify what a skill does and does not do, preventing scope creep before drafting the final specification.

How do I scope inputs and outputs for creative workflow ideation?

Creative workflow ideation scoping is facilitated by structured interviews that surface problem triggers, define inputs and outputs, and outline handoffs for the new skill.

Can I generate a complete SKILL.md file directly from an ideation interview?

You cannot generate a complete SKILL.md file directly, because this ideation partner only produces a ready-to-handoff Skill Specification artifact for the skill creator.

Do I need existing ecosystem documentation to align a new skill specification?

You need existing ecosystem documentation like TEAM.md and PIPELINE.md, because the interview process references them to ensure the new skill specification aligns with the factory.

When should I use an ideation interview instead of writing a skill spec myself?

You should use an ideation interview when you have an unstructured idea for a skill and need collaborative discovery to explore boundaries, inputs, and outputs before writing a spec.