본문으로 건너뛰기
cccskills
무료GitHub에 공개

interview

Scope a Claude Managed Agent through six questions about its job, trigger, inputs, actions, success criteria, and recurrence. Produce a validated build sheet with configuration components, deferred features, and an evaluation plan, without requiring an API key.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table + v1/v2 deferrals + eval plan) WITHOUT needing their API key yet. Use when the user says "help me scope an agent", "I have an idea for an agent", "what should this agent be", or when the orchestrator routes phase=interview. Drives the six intake slots (job, trigger, inputs, actions, definition-of-done, recurrence) via AskUserQuestion, maps them to primitives with interview_planner.py, assembles build-sheet.json with build_sheet_builder.py, and validates limits with primitives_validator.py. Connectors are mockable in v0 (schema-true custom tools); real MCP servers become v1 deferrals. Distinct from stage-launch (which turns the sheet into payloads).

연동 도구Gmail
설치 방법 보기

이럴 때 유용합니다

  • Turn an agent idea into a concrete build plan
  • Define success criteria before implementation
  • Separate the initial scope from later integrations
  • Plan an agent without providing an API key

포함된 파일(5)

  • SKILL.md4.3 KB
  • README.md1.1 KB
  • scripts/build_sheet_builder.py3.6 KB
  • scripts/interview_planner.py8.2 KB
  • scripts/primitives_validator.py6.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Phase 1 — Interview → Plan

Open warmly with one or two examples from ../../references/examples-bank.md, then interview the founder into a build sheet. No API key needed in this phase — the output is a plan.

The six intake slots (ask one at a time; use AskUserQuestion for choices)

SlotQuestionMaps to
Job"What one job should this agent do end-to-end?"agent.system + outcome description
Trigger"What kicks it off — you ask it, an event, or a schedule?"on-demand / event / cron
Inputs"What does it read?" (files, repo, memory, gmail/slack/github, web)resources / MCP servers / memory
Actions"What does it do?" (draft, write, call APIs, run code)agent toolset / custom tools / MCP
Done"How would you grade a good run?"outcome rubric (required)
Recurrence"Once, on request, or on a cadence?"single-pass / grade-loop / cron-loop

See ../../references/interview-to-config.md for the full mapping.

Workflow

  1. Interview. Walk the six slots. Capture the founder's own words — never invent specifics they didn't claim.
  2. Map to primitives.
    python3 scripts/interview_planner.py \
      --job "Triage overnight support email" --trigger schedule \
      --inputs "gmail,memory" --actions "label,reply" \
      --dod "one label per email, grounded reason, no invented facts" \
      --recurrence daily --out ./my-agent/plan.json
    
    MCP inputs become schema-true mock custom tools in v0 and a v1 deferral to wire the real server. Irreversible actions (send/publish) become v2 deferrals behind always_ask.
  3. Assemble the sheet.
    python3 scripts/build_sheet_builder.py --plan ./my-agent/plan.json --out-dir ./my-agent
    
  4. Validate limits.
    python3 scripts/primitives_validator.py --sheet ./my-agent/build-sheet.json
    
    FAIL blocks progress; fix and re-run. WARN is advisory (surface it).
  5. Record the plan in the goal. goal_state.py set --phase stage-launch --artifact build_sheet=./my-agent/build-sheet.json, then advance.

Hard rules

  • v0 is the core job only. Everything else is a versioned deferral with a reason and an exact mechanism.
  • Their problem, their words.
  • No key yet. The interview produces a plan; the key is a Phase-2 concern.

Forcing-question library (recommend + cite)

  1. "What one job — singular?" Recommend: the most-repeated task. Cite: interview-to-config.md. Two jobs → two agents.
  2. "Real integration or v0 mock?" Recommend: mock; wire MCP as v1. Cite: interview-to-config.md rule 1.
  3. "How do you grade it?" Recommend: 3–5 grounded rubric lines. Cite: cma-primitives.md (rubric required).
  4. "Smarter over time?" Recommend: attach memory only if yes. Cite: cma-primitives.md (memory limits + injection).
  5. "Once, or on a cadence?" Recommend: on-demand v0, schedule as Phase-4. Cite: loops-and-workflows.md.

Tools

  • scripts/interview_planner.py — answers → primitives skeleton + deferrals.
  • scripts/build_sheet_builder.py — assemble/normalize build-sheet.json.
  • scripts/primitives_validator.py — validate vs CMA limits (PASS/WARN/FAIL).

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills2.8만2026년 8월 30일 업데이트

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills2.8만2026년 8월 30일 업데이트

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills2.8만2026년 8월 30일 업데이트

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills2.8만2026년 8월 30일 업데이트

aeo

무료

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills2.8만2026년 8월 30일 업데이트

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills2.8만2026년 8월 30일 업데이트

alirezarezvani의 스킬 모두 보기

이 스킬의 문제 신고