agent-code-guide

Master guide for using Agent Code effectively. Includes configuration templates, prompting strategies "Thinking" keywords, debugging techniques, and best practices for interacting with the agent.

Quality

35%

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/agent-code-guide/SKILL.md

Quality

Discovery

32%

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

The description provides a reasonable overview of the skill's content areas but reads more like a table of contents than a selection guide. It lacks explicit trigger conditions ('Use when...') which is critical for Claude to know when to select this skill. The language is somewhat vague with terms like 'best practices' and 'effectively' rather than concrete actions.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks about agent configuration, prompting techniques, or debugging agent behavior'

Replace vague terms like 'best practices' and 'effectively' with specific capabilities like 'configure context windows, structure multi-step prompts, diagnose agent errors'

Include natural user phrases as triggers such as 'agent tips', 'how to prompt the agent', 'agent not working', 'agent setup'

Dimension	Reasoning	Score
Specificity	Names the domain ('Agent Code') and lists some actions ('configuration templates, prompting strategies, debugging techniques'), but these are categories rather than concrete specific actions like 'extract text' or 'fill forms'.	2 / 3
Completeness	Describes what it covers (configuration, prompting, debugging) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'Agent Code', 'prompting strategies', 'Thinking keywords', 'debugging', but missing natural user phrases like 'how to use agent', 'agent tips', 'agent help', or 'Claude agent'.	2 / 3
Distinctiveness Conflict Risk	'Agent Code' is somewhat specific, but 'prompting strategies' and 'best practices' are generic enough to potentially overlap with other guidance or meta-skills about using Claude effectively.	2 / 3
	Total	7 / 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 is essentially a skeleton or placeholder - it has good structure and is concise, but lacks any actual actionable content. The description promises 'configuration templates, prompting strategies, debugging techniques, and best practices' but the body delivers only links to sub-skills without any standalone value or overview guidance.

Suggestions

Add a concrete 'Quick start' section with an actual CLAUDE.md template example that users can copy-paste

Include at least one executable example of a prompting strategy or thinking keyword usage directly in the main skill

Provide brief summaries of what each sub-skill contains so users know which to reference without clicking through

Add a basic workflow showing when to use each sub-skill (e.g., 'Starting a project? Use Template. Stuck? Use Debugging.')

Dimension	Reasoning	Score
Conciseness	The content is extremely lean with no unnecessary explanations. Every line serves a purpose - it's essentially a navigation hub with minimal overhead.	3 / 3
Actionability	The skill provides no concrete guidance, code, or executable instructions. It only describes what exists ('create a CLAUDE.md file') without showing how or providing any actual content, templates, or examples.	1 / 3
Workflow Clarity	There is no workflow defined. The skill mentions 'configuration templates, prompting strategies, debugging techniques' in the description but provides none of these - just links to sub-skills without any sequencing or process guidance.	1 / 3
Progressive Disclosure	The skill attempts progressive disclosure by linking to sub-skills, but the main file provides almost no overview content. It's essentially an empty table of contents without the 'Quick start' or summary content that would make the references meaningful.	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: 332e58b

Reviewed: 17 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.