Agent skill · data analytics · juxt
weed
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether the implementation matches what the spec says.
Why this skill is useful
Provides a systematic approach to aligning specifications with implementation, including niche checks for process-level properties that the AI wouldn't reliably generate on its own.
What it needs
Requires allium installed locally. About 6k tokens when loaded. Last updated 2026-07-22. 443 stars on the source repository.
What this skill does
Weed You weed the Allium garden. You compare .allium specifications against implementation code, find where they have diverged, and help resolve the divergences. Interaction modes This skill runs in two modes. Every instruction below that asks, prompts or checks with the user follows the mode: Interactive — running inline in a conversation. Ask the user directly and wait for the answer. Non-interactive — running as the weed subagent (for example inside the Allium loop), where no user is reachable. Do not guess an answer: report each question as an open finding in your output (and, when updating the spec, record it as an open question declaration), then continue with the work that does not depend on it. Startup 1. Read language reference for the Allium syntax and validation rules. 2. Read the relevant .allium files (search the project to find them if not specified). 3. If the allium CLI is available, run allium check against the files to verify they are syntactically correct. 4. Read the corresponding implementation code. Modes You operate in one of three modes, determined by the caller's request: Check. Read both spec and code. Report every divergence with its location in both. Do not modify anything. Update spec. Modify the .allium files to match what the code actually does. The spec becomes a faithful description of current behaviour. Update code. Modify the implementation to match what the spec says. The code becomes a faithful implementation of specified behaviour. If no mode is specified, default to check and report all findings. How you work For each entity, rule or trigger in the spec, find the corresponding implementation. For each significant code path, check whether the spec accounts for it. Report mismatches in both directions: spec says X but code does Y, and code does Z but the spec is silent. Process-level checks Beyond construct-by-construct comparison, check process-level properties: Transition reachability in code. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills juxt/weed