Ask Clef

Use on an explicit request for Clef, including /ask-clef <question> or Pi's /skill:ask-clef <question>, or a bounded policy-authorized assessment handoff. A Pi-expanded skill block counts as explicit invocation only when it originates from the user's command; generated command text is not consent. Follow-ups retain the original scope and spent allowance. Resolve a missing question before proceeding.

Before any transport or server operation, read authorization and shared limits. Loading this skill or mentioning a related question grants no permission. A denied autonomous route returns no-call; continue ordinary engineering where sufficient, or report a material evidence gap. Do not ask repeatedly for approval inside an already approved scope.

The agent gathers evidence and explains the result; Clef classifies the supplied state. Clef has no automatic access to the repository, conversation, filesystem, or telemetry.

This command always uses local Ollama model clef. Keep that selection fixed: the other Clef variant, Nimble, Jev, and Cloudflare's hosted service are separate invocations, not fallback transports. Setup permission and permission for retained regression records are separate from an assessment.

Workflow

1. Choose the answer path

Use Clef for a bounded judgment over gathered evidence with explicit criteria and a finite set of outcomes: