vague

1 stars
14
A

Use when writing Vague (.vague) files - a declarative language for generating realistic test data with superposition, constraints, and cross-references

Also in: data analysis

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/vague
skilz install mcclowes/omg/vague --agent opencode
skilz install mcclowes/omg/vague --agent codex
skilz install mcclowes/omg/vague --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/mcclowes/omg
2. Copy the agent skill directory:
cp -r omg/.claude/skills/vague ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

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

Spec Compliance
12/15
PDA Architecture
29/30
Ease of Use
24/25
Writing Style
10/10
Utility
19/20

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, and cli.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...

Report Security Issue

Found a security vulnerability in this agent skill?