CCARF Practice Question

Paper 3 · Question 36

D3 Claude Code Configuration & Workflows · Paper 3

[Scenario 4: Developer Productivity with Claude] You are building developer productivity tooling on the Claude Agent SDK: helping engineers explore unfamiliar codebases, understand legacy systems, generate boilerplate, and automate repetitive tasks — using the built-in tools (Read, Write, Edit, Bash, Grep, Glob) plus MCP servers. Developers keep invoking your /generate-fixture skill bare, without the entity type and record count it needs, then get confused by the results. Which frontmatter option addresses this?

• A.context: fork, isolating the confusion in a subagent
• B.allowed-tools, restricting what the skill can touch
• C.A longer skill description explaining the parameters
• D.argument-hint, which prompts developers for the required parameters when the skill is invoked without arguments

Show answer & explanations

Correct answer: D

A: isolates output, not input requirements

B: constrains tools, not arguments

C: documents the parameters for whoever reads docs — the invocation still runs bare

D: argument-hint is the frontmatter mechanism for exactly this: skills that need parameters can prompt for them on bare invocation instead of running underspecified.

Related Claude Code Configuration & Workflows questions

More: Paper 3 · All practice questions