.claude/skills/agency-client-interview/SKILL.md
Client discovery interview framework for AI Agency projects covering business objectives, audience analysis, brand context gathering, and structured question flows that adapt to user patterns over time.
npx skillsauth add modu-ai/moai-adk agency-client-interviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Governs the client discovery process for AI Agency projects. Provides structured question flows, progressive disclosure of interview depth, and context file generation for .agency/context/.
Purpose: Define interview question frameworks, context gathering strategies, and structured output formats for populating .agency/context/ files during project onboarding.
Input Contract:
.agency/context/ files (may be empty on first run)Output Contract:
.agency/context/ files:
brand-voice.md — tone, style, language preferencestarget-audience.md — customer personas, pain pointsvisual-identity.md — colors, fonts, imagery preferencestech-preferences.md — framework, hosting, integrationsquality-standards.md — performance targets, accessibility levelOwner: .agency/context/target-audience.md
Derived from Brand Context. Never auto-modified. Manual editing only.
Phase 1: Business Context (3 questions)
Phase 2: Brand Identity (3 questions) 4. How would you describe your brand voice? (3-5 adjectives) 5. Are there reference sites or brands you admire? 6. Any design preferences or constraints? (colors, style, existing brand guidelines)
Phase 3: Technical Scope (2 questions) 7. What pages/sections do you need? 8. Any technical requirements? (framework, hosting, integrations)
Phase 4: Quality Expectations (1 question) 9. What matters most to you? (speed, design quality, mobile experience, SEO)
.agency/context/ files already have content, skip covered questionsInterview questions, order, and depth evolve via user feedback.
(No rules yet. Rules will be added as the system learns from user feedback.)
(No anti-patterns yet.)
(No heuristics yet.)
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------
tools
A CLI tool for making authenticated requests to the X (Twitter) API. Use this skill when you need to post tweets, reply, quote, search, read posts, manage followers, send DMs, upload media, or interact with any X API v2 endpoint.