vague
Use when writing Vague (.vague) files - a declarative language for generating realistic test data with superposition, constraints, and cross-references
Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security
Installation for Agentic Skill
View all platforms →skilz install mcclowes/omg/vagueskilz install mcclowes/omg/vague --agent opencodeskilz install mcclowes/omg/vague --agent codexskilz install mcclowes/omg/vague --agent geminiFirst time? Install Skilz: pip install skilz
Works with 22+ AI coding assistants
Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...
Extract and copy to ~/.claude/skills/ then restart Claude Desktop
git clone https://github.com/mcclowes/omgcp -r omg/.claude/skills/vague ~/.claude/skills/Need detailed installation help? Check our platform-specific guides:
Related Agentic Skills
pytest-config
by athola
Standardized pytest configuration patterns for plugin development. Reducesduplication across parseltongue, pensive, sanctum, and other plugins.Trig...
shell-testing-framework
by manutej
Shell script testing expertise using bash test framework patterns from unix-goto, covering test structure (arrange-act-assert), 4 test categories, ...
markdownlint-custom-rules
by TheBushidoCollective
Create custom linting rules for markdownlint including rule structure, parser integration, error reporting, and automatic fixing.
feature-dev
by secondsky
Automate 7-phase feature development with specialized agents (code-explorer, code-architect, code-reviewer). Use for multi-file features, architect...
Agentic Skill Details
- Repository
- omg
- Stars
- 1
- Type
- Technical
- Meta-Domain
- development
- Primary Domain
- testing
- Market Score
- 14
Agent Skill Grade
A Score: 94/100 Click to see breakdown
Score Breakdown
Areas to Improve
- Missing TOCs in Long Files
- Limited Troubleshooting Guidance
Recommendations
- Add trigger phrases to description for discoverability
- Add table of contents for files over 100 lines
Graded: 2026-01-24
Developer Feedback
I've been exploring how skills handle ambiguous requirements, and yours takes an interesting approach to that problem—your 94 score reflects solid execution across the board, but I'm curious whether the vagueness is intentional design or something worth tightening up.
Links:
The TL;DR
You're at 94/100, solidly in A territory. This is based on Anthropic's skill best practices. Your strongest pillar is Writing Style (10/10—zero fluff, tight voice throughout), but Spec Compliance (12/15) is where you're leaving points on the table. The PDA architecture is excellent; reference layering is exactly what you want.
What's Working Well
- Writing style is chef's kiss. No "you" anywhere, pure imperative voice, optimal token density. The Quick Start in SKILL.md and the examples across all four reference files show exactly what developers need without the noise.
- Reference architecture nails the layering. 48 lines in SKILL.md, with everything else distributed across
syntax.md,functions.md,plugins.md, andcli.md. That's how you do PDA right—main file gets straight to the point, details live elsewhere. - Strong trigger phrases for discoverability. "Vague files", ".vague", "declarative language", "test data", "superposition"—these activate appropriately when someone's actually wrestling with test data generation.
- Utility is comprehensive. The Invoice, Player, and TimeSeries examples cover realistic patterns, and the superposition + constraints combo addresses a genuine gap in test data tooling.
The Big One: Spec Compliance Gap
You're at 12/15 here, and it's fixable. The issue: your description only has 1-2 trigger phrases, but the spec wants more discoverability hooks. Right now your description says "writing Vague (.vag...
Browse Category
More development Agentic SkillsReport Security Issue
Found a security vulnerability in this agent skill?
Report Security Issue
Thank you for helping keep SkillzWave secure. We'll review your report and take appropriate action.
Note: For critical security issues that require immediate attention, please also email security@skillzwave.ai directly.