brainstorming

Socratic questioning protocol + user communication.

Quality

18%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/brainstorming/SKILL.md

Quality

Discovery

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

This description is critically underdeveloped. It provides no concrete actions, no trigger terms users would naturally use, and no guidance on when Claude should select this skill. The vague phrasing makes it nearly impossible to distinguish from other skills or understand its purpose.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Guides users through problem-solving by asking clarifying questions, breaks down complex problems into smaller parts, helps users discover solutions themselves')

Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user seems stuck, asks for help thinking through a problem, or when clarifying questions would help understand requirements')

Replace jargon like 'Socratic questioning protocol' with user-friendly language that describes the actual behavior and outcomes

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('Socratic questioning protocol', 'user communication') without listing any concrete actions. It does not specify what the skill actually does.	1 / 3
Completeness	Missing both 'what' and 'when'. The description does not explain what actions the skill performs nor when Claude should use it. There is no 'Use when...' clause or equivalent guidance.	1 / 3
Trigger Term Quality	Contains no natural keywords users would say. 'Socratic questioning protocol' is technical jargon, and 'user communication' is overly generic. Users would not naturally use these terms when seeking help.	1 / 3
Distinctiveness Conflict Risk	'User communication' is extremely generic and could conflict with virtually any skill that involves interacting with users. 'Socratic questioning' is slightly more specific but still unclear in scope.	1 / 3
	Total	4 / 12 Passed

Implementation

37%

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

This skill file is essentially an empty shell - a pure index with no substantive content. While concise, it fails to provide any actionable guidance, workflow clarity, or even a brief overview of what the Socratic questioning protocol actually involves. A skill file should be usable on its own with references for depth, not require reading 11 separate files to understand the basics.

Suggestions

Add a 'Quick Start' section with the core 3-question protocol inline so the skill is immediately actionable without reading sub-files

Include at least one concrete example of the Socratic questioning flow (trigger → questions → decision point)

Add a brief workflow summary showing the sequence: when triggered → ask questions → evaluate answers → proceed or iterate

Provide a minimal inline version of the question format so Claude can use the skill without loading all sub-files

Dimension	Reasoning	Score
Conciseness	The content is extremely lean - just a brief description and a list of sub-skill references. No unnecessary explanation or padding.	3 / 3
Actionability	The skill body contains zero concrete guidance, no examples, no executable steps - it's purely a table of contents pointing elsewhere with no actionable content in the main file.	1 / 3
Workflow Clarity	Despite being about a 'protocol', there's no workflow visible in this file - no sequence, no steps, no validation checkpoints. The numbered list is just navigation, not a process.	1 / 3
Progressive Disclosure	References are one level deep and clearly signaled, but the main file provides no overview or quick-start content - it's entirely empty of substance, making it impossible to understand the skill without reading all 11 sub-files.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Dokhacgiakhoa/antigravity-ide
Commit: 3395991

Reviewed: 24 days ago

Table of Contents

Discovery Implementation Validation

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.