/ouroboros:idk

Calibrate the language used by ooo interview without weakening the interview itself.

Usage

ooo idk <terms I do not know, or what I understand about them>
/ouroboros:idk <terms I do not know, or what I understand about them>

Examples:

ooo idk I do not know idempotency or event sourcing. I have built REST APIs.
ooo idk Kubernetes: deployed a tutorial once; networking and operators are unfamiliar.
ooo idk OAuth is familiar enough to implement, but I cannot explain PKCE.

Instructions

When the user invokes this skill, treat their text as evidence for a conversation-local interview calibration, not as a test and not as a permanent rating of the person.

1. Extract evidence without quizzing by default

Identify:

• terms or concepts the user explicitly does not know;
• concepts they recognize but cannot explain or apply;
• concepts they can explain, use, debug, or compare;
• concrete experience they report, such as tutorials, production use, or design work.

Use only what the user actually said. Do not infer low general ability from one unknown term, unfamiliar English vocabulary, a typo, or a short answer. Ask one short follow-up only when the supplied text is too ambiguous to affect interview wording safely. Otherwise continue immediately.

2. Estimate a local level and confidence

Assign one overall interview explanation level based on the user's evidence:

• Foundational, use plain language, define necessary terms before using them, and give one concrete example.
• Working, use standard terminology with a short definition when a term is new or overloaded; connect questions to practical trade-offs.
• Fluent, use precise domain terminology and concise trade-off language; skip definitions unless requested.