Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/expertise-file-design
Design YAML expertise file structures for agent experts.
Passed 20 of 22 test cases with the skill, and 4 of 22 without it.
and 26 more in the full report
17 fixed3 passed either way1 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
What four comment fields must appear in the top header block of every expertise YAML file?
| Checked | Without skill | With skill |
|---|---|---|
| Includes file path comment specifying domain expertise location. | Missed | Passed |
| Includes last updated timestamp and line count status comments. | Missed | Passed |
The instructions your model reads when the skill loads.
Guide for designing YAML expertise files that serve as mental models for agent experts.
Expertise files are mental models, NOT sources of truth. They:
# {domain}/expertise.yaml
# Mental model for {domain} agent expert
# Last updated: {timestamp}
# Lines: {current}/{max}
overview:
description: "Brief description of this domain"
primary_technology: "Main tech/framework"
architecture_pattern: "Key pattern used"
core_implementation:
main_module:
file: "path/to/main/file.ext"
lines: approximate_line_count
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.