context-manager

Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems.

Quality

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/context-manager/SKILL.md

Quality

Content

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 persona/role description rather than an actionable skill file. It consists almost entirely of abstract capability lists and behavioral descriptions that Claude already understands, with zero concrete code, commands, or specific implementation guidance. The content would need to be fundamentally restructured from a 'who you are' document into a 'what to do and how' document with executable examples and clear workflows.

Suggestions

Replace the extensive capability bullet lists with 2-3 concrete, executable workflow examples (e.g., a specific RAG implementation with code, a vector database setup with actual commands)

Create the referenced 'resources/implementation-playbook.md' bundle file and move detailed patterns there, keeping SKILL.md as a concise overview under 50 lines

Add specific validation checkpoints for key workflows (e.g., 'After setting up vector index, verify with: `curl localhost:6333/collections` and confirm collection exists')

Remove the 'Capabilities', 'Behavioral Traits', 'Knowledge Base', and 'Example Interactions' sections entirely — these describe what Claude already knows rather than providing new, actionable instructions

Dimension	Reasoning	Score
Conciseness	Extremely verbose and padded with content Claude already knows. The massive 'Capabilities' section is essentially a laundry list of AI/ML concepts that Claude is already deeply familiar with. 'Behavioral Traits', 'Knowledge Base', and 'Example Interactions' sections add no actionable value. The skill reads like a persona description or job posting rather than a concise instruction set.	1 / 3
Actionability	No concrete code, commands, specific tools configurations, or executable examples anywhere. The entire skill is abstract descriptions ('Dynamic context assembly and intelligent information retrieval') with no specific implementation guidance. The 'Response Approach' is a generic 10-step process with no concrete details. References 'resources/implementation-playbook.md' but provides no bundle file.	1 / 3
Workflow Clarity	The 10-step 'Response Approach' is vague and generic (e.g., 'Analyze context requirements', 'Design context architecture') with no validation checkpoints, no error recovery, and no concrete sequencing. There are no specific workflows for any of the many tasks this skill claims to cover.	1 / 3
Progressive Disclosure	The skill is a monolithic wall of text with hundreds of bullet points inline. It references 'resources/implementation-playbook.md' but no bundle files exist. The massive capability lists should be in separate reference files, with the SKILL.md providing only a concise overview and actionable quick-start guidance.	1 / 3
	Total	4 / 12 Passed

Description

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 reads like a resume headline rather than a functional skill description. It is packed with buzzwords ('elite', 'mastering', 'intelligent') but lacks any concrete actions, explicit trigger conditions, or clear scope boundaries. It would be nearly impossible for Claude to reliably select this skill over others based on this description.

Suggestions

Replace buzzword-heavy language with specific concrete actions, e.g., 'Builds and queries vector databases, constructs knowledge graphs from unstructured data, manages conversation context windows.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about embedding storage, semantic search, RAG pipelines, or managing long-context conversations.'

Narrow the scope to a distinct niche—covering vector databases, knowledge graphs, AND memory systems is too broad. Pick a focused domain or clearly delineate sub-capabilities to reduce conflict risk with other skills.

Dimension	Reasoning	Score
Specificity	The description uses vague, buzzword-heavy language like 'elite AI context engineering specialist' and 'mastering dynamic context management' without listing any concrete actions. No specific tasks like 'builds knowledge graphs', 'indexes documents into vector databases', or 'manages conversation memory' are described.	1 / 3
Completeness	The description fails to answer both 'what does this do' (no concrete actions) and 'when should Claude use it' (no 'Use when...' clause or equivalent trigger guidance). It reads as a self-promotional tagline rather than a functional description.	1 / 3
Trigger Term Quality	The terms used ('context engineering', 'vector databases', 'knowledge graphs', 'intelligent memory systems') are technical jargon that users are unlikely to naturally say when requesting help. A user would more likely say 'store embeddings', 'search my documents', or 'remember previous conversations'.	1 / 3
Distinctiveness Conflict Risk	The description is extremely broad, covering multiple domains (vector databases, knowledge graphs, memory systems, context management) without clear boundaries. It could easily conflict with any skill related to databases, AI, memory, or knowledge management.	1 / 3
	Total	4 / 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: sickn33/antigravity-awesome-skills
Commit: 88d1e11

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