CtrlK
BlogDocsLog inGet started
Tessl Logo

thinking-out-loud

A contract for what the agent does when a long, messy, stream-of-consciousness ramble arrives (usually voice dictation): act on nothing until the echo brief is approved. The echo audits the entire transfer, mission, locked decisions and constraints, open questions, flips and parked tangents, with the model's inferences and guesses quarantined away from the user's own phrasing, so the user verifies what the model believes, not just what it doubts. Use when the user says "let me think out loud" or wants to ramble a bit before building anything, when a message opens with a speech-to-text preamble like "switching to voice, sorry for typos", when input is a long weakly punctuated stream with restarts and mid-message reversals ("actually no, wait, scrap that idea entirely"), or when the user asks to be interviewed about a fuzzy half-formed idea. Includes an optional capture mode for rambles spread across several messages and an optional targeted interview.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, well-structured instruction skill that gives concrete, copy-paste-ready behavioral rules and appropriately offloads the full template and worked example to a single clearly signaled reference. The main improvement is tightening the motivational rationale, which slightly overlaps itself.

Suggestions

Collapse the intro and "Why an echo instead of follow-up questions" into one shorter rationale; the silent-gap-fill point is made twice.

Make the correction retry loop explicit in the contract (e.g. "If the user corrects the echo, re-issue only the changed sections before acting").

DimensionReasoningScore

Conciseness

Mostly lean and instructional, but the opening problem statement and "Why an echo instead of follow-up questions" section restate the same gap-filling insight and could be trimmed without losing guidance.

4 / 5

Actionability

Highly concrete behavioral guidance: a six-rule contract, a five-section echo template with non-negotiable compression rules, exact capture-mode acknowledgment lines, named exit triggers, and three explicit persistence options.

5 / 5

Workflow Clarity

Clear sequence with an explicit approval gate ("Act on nothing... until the echo is approved") and a correction invitation checkpoint, but the retry loop on rejection is implied rather than spelled out.

4 / 5

Progressive Disclosure

Well-organized sections with a single one-level-deep reference, clearly signaled as "Full template with a worked example in references/echo-format.md", which exists and holds the detailed template and example.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: third-person, concrete in its actions, explicit about both capability and trigger conditions, and tightly scoped to a distinctive niche. Its only weakness is verbosity — it is longer than necessary for the density of information it carries.

Suggestions

Trim the explanatory clauses (e.g. "so the user verifies what the model believes, not just what it doubts") to tighten the description without losing trigger specificity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "act on nothing until the echo brief is approved", audits mission/locked/open/flips/parked tangents, quarantines inferences, plus optional capture mode and targeted interview — with comprehensive coverage and no real gaps.

5 / 5

Completeness

Explicitly answers both what (a contract to produce an echo brief before acting) and when, with a dedicated "Use when" clause listing concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes exact natural phrases users would say — "let me think out loud", "switching to voice, sorry for typos", "actually no, wait, scrap that idea entirely", "interviewed about a fuzzy half-formed idea" — with strong synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — voice-dictated stream-of-consciousness rambles needing an audit before action — with distinctive triggers and minimal overlap with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Shubhamsaboo/awesome-llm-apps
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.