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 masquerading as a skill file. It consists almost entirely of abstract capability listings, behavioral traits, and knowledge areas that provide no actionable guidance for performing any specific task. The content is extremely verbose with no concrete code, commands, examples, or validation steps, making it nearly useless as an operational skill.

Suggestions

Replace the abstract capability listings with concrete, executable examples for 2-3 core tasks (e.g., a working RAG implementation, a vector DB setup with specific code, a knowledge graph query example).

Add specific validation and verification steps for key workflows like RAG pipeline setup, vector database indexing, or knowledge graph construction, including error recovery loops.

Remove the 'Capabilities', 'Behavioral Traits', and 'Knowledge Base' sections entirely — these describe what Claude should be rather than what Claude should do, and Claude already understands these concepts.

Create the referenced `resources/implementation-playbook.md` with detailed worked examples, and move any necessary reference material into properly structured bundle files.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and padded with extensive lists of capabilities, behavioral traits, and knowledge areas that Claude already knows. The content reads like a persona description rather than actionable instructions. Most of the 150+ lines are abstract capability listings that add no concrete value.	1 / 3
Actionability	No concrete code, commands, or executable guidance anywhere. The entire skill is abstract descriptions ('Dynamic context assembly and intelligent information retrieval') and vague bullet points. The 'Response Approach' section lists generic steps like 'Analyze context requirements' without any specifics. 'Example Interactions' are just prompts, not worked examples.	1 / 3
Workflow Clarity	The 'Response Approach' lists 10 generic steps with no validation checkpoints, no error recovery, and no concrete sequencing. There are no feedback loops or verification steps for any of the complex operations described (vector DB setup, knowledge graph construction, RAG implementation).	1 / 3
Progressive Disclosure	There is one reference to `resources/implementation-playbook.md` for detailed examples, which is a reasonable attempt at progressive disclosure. However, no bundle files exist to support this reference, and the massive inline content (capabilities, behavioral traits, knowledge base) should have been split into separate reference files rather than dumped into the main skill body.	2 / 3
	Total	5 / 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 perform very poorly in a skill selection scenario with multiple available skills.

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 conversation context.'

Narrow the scope to a distinct niche to reduce conflict risk — currently it spans at least 4 different domains (vector DBs, knowledge graphs, memory systems, context management) that could each be separate 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 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: 6042393

Reviewed: about 2 hours 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.