agent-context-loader
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill agent-context-loaderExecute proactive auto-loading: automatically detects and loads agents.md files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content is a generic template with no actual implementation. It claims to auto-detect and load agents.md files but provides zero specifics about how detection works, what triggers loading, or what the loaded content does. The entire body could be replaced with 'TODO: write actual skill content' and convey the same information.
Suggestions
Add concrete code showing how to detect agents.md files (e.g., file path patterns, detection triggers, glob patterns)
Define specific trigger phrases or context patterns that activate this skill
Provide an executable example of loading and processing an agents.md file
Replace generic placeholder steps with actual workflow: detect file → read content → parse/validate → apply context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely generic boilerplate with no specific information about agent context loading. Every section contains placeholder text that could apply to any skill, wasting tokens on content that provides zero value. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. Steps like 'Execute skill workflow systematically' and 'Handle errors and edge cases appropriately' are completely vague and non-actionable. | 1 / 3 |
Workflow Clarity | The numbered steps are abstract placeholders with no actual sequence for detecting or loading agents.md files. No validation checkpoints, no specific triggers defined, no concrete workflow for the stated purpose. | 1 / 3 |
Progressive Disclosure | References to external files (errors.md, examples.md) are present and one-level deep, but the main content is so empty that the structure serves no purpose. The referenced files may not even exist. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
7%This description is essentially a template with placeholder text that was never filled in. It fails to explain what agents.md files are, why loading them matters, or provide any concrete trigger terms. The circular 'Use when appropriate context detected' and 'Trigger with relevant phrases based on skill purpose' provide zero guidance for skill selection.
Suggestions
Replace placeholder text with actual trigger terms - specify what user requests or contexts should activate this skill (e.g., 'Use when user mentions agents, automation workflows, or asks to load agent configurations')
Explain what agents.md files are and what benefit loading them provides (e.g., 'Loads agent configuration files that define automated workflows and behaviors')
Add concrete examples of when this skill applies versus when it doesn't to help distinguish it from other file-loading skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'automatically detects and loads' without explaining what agents.md files are or what happens after loading. 'Appropriate context' and 'relevant phrases based on skill purpose' are abstract placeholders, not concrete actions. | 1 / 3 |
Completeness | The 'what' is extremely weak (just 'detects and loads agents.md files' with no explanation of purpose). The 'when' clause ('appropriate context detected', 'relevant phrases based on skill purpose') is entirely circular and provides no actionable guidance. | 1 / 3 |
Trigger Term Quality | The only specific term is 'agents.md files' which is technical jargon. 'Relevant phrases based on skill purpose' is a meta-placeholder that provides zero actual trigger terms users would say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'agents.md files' provides some specificity that distinguishes it from generic document skills, but the vague trigger language could cause conflicts with any skill that involves loading or detecting files. | 2 / 3 |
Total | 5 / 12 Passed |
Reviewed
Table of Contents
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.