bassclef
SkillsConcept
LitePhase ConceptAlso useful in DesignBody 2 sections · ~170 wordsUpdated 2026-10-02

/interpret-input

Turn any input into a schema-valid InputArtifact. Modes: text, URL, image, repo, transcript, napkin, mixed. text + repo ship today. Others return valid stubs. First step of the cameo pipeline.

Copy the command
/interpret-input
/interpret-input text
/interpret-input url
/interpret-input image
/interpret-input repo
/interpret-input transcript
/interpret-input napkin
/interpret-input mixed

Type it bare, or paste it with loose context after — Claude figures out the rest.

Solves

Different sessions start with different input shapes — text or URL or image or repo or transcript.

Payoff

One schema-validated artifact from any input. Downstream skills read one shape not seven.

Takes in

  • Any input — text or URL or image or repo ref or transcript

Returns

  • A schema-validated InputArtifact with kind and content
Runs with
—
Needs first
—
Called by
—
Deep dive — 2 sections · ~170 words · original SKILL.mdScroll for tutorial ↓

What it does

First-step skill of the cameo pipeline. It takes operator input (text from phone, URLs, screenshots, repos) and returns schema-valid InputArtifact JSON. Downstream skills read it via the typed accessor library.

This is the bassclef-side interface for the cameo fanout pipeline. Every input type maps to the same downstream payload.

Read the full skill

The complete instructions live at .claude/skills/interpret-input/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.

Where in the SDLC

Also relevant in: Design.

Why this phase: Reads external input into InputArtifact — the first step of any /launch or /stage chain.

FAQ

Terms from bassclef vocabulary that appear on this page.

cameo
A pattern for routing a specific practitioner's documented judgment into a specific software development task. Bassclef implements it as three parts — a curated catalog of practitioners, a matcher that connects problems to relevant experts, and invokable skills that channel the pick. You see 'Cooper says X' or 'Norman flags Y' inline rather than the skill running a full consult. Trades depth for speed on lower-stakes surfaces. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
luminary
A design or engineering thinker whose discipline bassclef borrows as a review lens — the practitioner in the cameo pattern above. Cooper for personas, Norman for signifiers, Feathers for characterization tests, Beck for TDD rhythm, plus about 90 others. Skills invoke a lens to check work against a specific discipline. `/luminary` browses the catalog. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
hook
A shell script bassclef wires into Claude Code's tool-invocation lifecycle. Hooks fire at events like PreToolUse (before an Edit lands) or SessionStart (when a session opens). Hooks enforce rules mechanically — a rule says 'don't do X'; a hook fires and BLOCKs if X happens.
rule
A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
skill
A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
adopter
A repo that has bassclef installed — either via `bassclef init` (lite tier from npm) or via the symlink pattern (standard tier with an Anthropic key). Bassclef's discipline: never break adopters. Every change to a downstream-observable surface ships with a compat shim.

Shipped by @kingofrock · Read the essays

On this page

© 2025–2026 Sunjay Pandey·Privacy·Apache-2.0 code