toy-tidy

Audits the Lia Tools folder structure against its convention and reports or fixes drift.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill toy-tidy-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: toy-tidy
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/toy-tidy
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill toy-tidy-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Information flows into the Products/Lia Tools folder from feedback videos, build sessions, research, and jams, and over time the structure drifts from its documented convention. This Skill sweeps the whole toy line, reports every drift item, fixes the mechanical issues on request, and proposes the judgment calls for a human decision. ## Core Features & Use Cases - Convention Sweep: Checks folder shape (six numbered stages plus unnumbered layers), the tools table against folders and Linear epics, meeting notes, feedback wiring, handover records, index rows, freshness, and frontmatter. - Report and Fix Modes: Report mode reads everything and writes nothing, producing a drift table; fix mode applies only mechanical fixes (missing folders, index rows, broken links, frontmatter) and never edits records or deletes files. - Use Case: After a heavy stretch of toys work, ask for a tidy to verify every tool has the right stage folders, every meeting note is wired to its transcript and feedback summary, and each thread has exactly one active After Action Report. ## Quick Start Ask the agent to tidy the toys folder and report any drift against the Lia Tools convention.

Frequently Asked Questions about toy-tidy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the Lia Tools folder structure for drift?▼

Ask for a toy tidy in report mode, which is the default. The sweep checks folder shape, the tools table against Linear epics, meeting notes, feedback wiring, records, index rows, freshness, and frontmatter, then outputs a drift table classifying each finding as mechanical or judgment.

How do I fix folder structure drift automatically?▼

Explicitly ask for fix mode, for example by saying fix the toys drift. Fix mode applies only mechanical fixes such as creating missing convention folders, adding index rows, repairing broken links, and completing frontmatter, while judgment calls are still proposed rather than made.

Can the tidy skill delete or edit old handover records?▼

No. Handovers and retro entries are treated as records and are never edited, and nothing is ever deleted. Items may only be moved to a _to_delete folder with explicit approval, and retired paths inside dated records are flagged as history, not repaired.

What counts as drift in the toys folder convention?▼

Drift includes folders with retired or off-convention names, tools missing from the README table or Linear, meeting notes with unfinished video fields, feedback summaries not linked to meeting notes, threads with two active reports, missing index rows, stale freshness lines, and incomplete frontmatter.

When should I run a folder tidy versus doing it manually?▼

Run it on demand after a heavy stretch of work when information has flowed in and structure may have lagged. It is never scheduled, and report mode is safe to run anytime since it writes nothing.