oracle

System architect and design expert - provides strategic technical guidance

Quality

21%

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 ./skills/oracle/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 weak across all dimensions. It reads as a job title rather than a skill description, providing no concrete actions, no natural trigger terms, and no guidance on when Claude should select this skill. It would be nearly impossible for Claude to reliably choose this skill over others in a multi-skill environment.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates system architecture diagrams, evaluates scalability patterns, designs microservice boundaries, reviews technical trade-offs'

Include a 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about system design, architecture decisions, scaling strategies, or technical trade-offs'

Add file types or specific domains to increase distinctiveness, e.g., 'distributed systems, API design, database schema design, cloud architecture'

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'strategic technical guidance' without listing any concrete actions. It describes a role rather than specific capabilities.	1 / 3
Completeness	Missing both clear 'what' (no specific actions listed) and 'when' (no 'Use when...' clause or explicit trigger guidance). The description only vaguely implies a domain without answering either question.	1 / 3
Trigger Term Quality	Contains only generic technical jargon ('system architect', 'design expert', 'strategic technical guidance') that users are unlikely to naturally say when seeking help. Missing natural trigger terms like 'architecture diagram', 'system design', 'scalability', etc.	1 / 3
Distinctiveness Conflict Risk	Extremely generic - 'technical guidance' could overlap with virtually any technical skill. 'System architect' and 'design expert' are broad roles that don't carve out a clear niche.	1 / 3
	Total	4 / 12 Passed

Implementation

42%

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

This skill defines a persona and high-level approach for architecture decisions but lacks the concrete, actionable guidance that makes skills effective. It describes what to think about rather than providing specific techniques, example outputs, or executable patterns. The structure is good but the content is too abstract to meaningfully guide Claude's behavior beyond what it would already do.

Suggestions

Replace abstract example scenarios with concrete input/output examples showing actual architecture recommendations with specific technical details

Add executable artifacts like architecture decision record templates, specific questions to ask for each scenario type, or checklists for common decisions

Remove the principles section (Claude knows these) and the persona framing - focus on what specific behaviors or outputs differ from Claude's defaults

Include specific tools, commands, or analysis techniques (e.g., 'Run EXPLAIN ANALYZE on slow queries' rather than 'Identify bottlenecks')

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary elements like the philosophical quote at the end and the persona framing ('Oracle - The Architect's Vision') that don't add actionable value. The principles section states things Claude already knows.	2 / 3
Actionability	The skill provides abstract guidance rather than concrete, executable instructions. Example scenarios describe what to consider but don't provide specific commands, code, or copy-paste ready outputs. 'Analyze project requirements' and 'Identify bottlenecks' are vague directions, not actionable steps.	1 / 3
Workflow Clarity	The 'Approach' section provides a clear 4-step sequence, and the 'Output Format' gives structure. However, there are no validation checkpoints or feedback loops for when recommendations don't work or need iteration. The steps are high-level without concrete verification points.	2 / 3
Progressive Disclosure	For a skill of this size (~60 lines) focused on a single domain (architecture guidance), the content is well-organized with clear sections. No external references are needed, and the structure allows easy navigation between use cases, approach, and output format.	3 / 3
	Total	8 / 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: TurnaboutHero/oh-my-antigravity
Commit: fab464f

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.