toy-status

Assembles a live status table of Lia Tools toys from Linear, release registers, and vault records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Getting the current state of the Lia Tools product line normally requires reading four folders and a Linear board by hand. This Skill assembles that picture fresh from live sources on demand, so every status line traces to something checkable instead of stale memory. ## Core Features & Use Cases - Live multi-source status table: For each toy and the toolbox, pulls stage and version from the release register, board counts from Linear, the latest feedback headline, and open jam items. - Honesty over guessing: Never invents a Linear status, version, or stage; if a source is unreachable it reports "unreadable from here" for that column. - Drift detection: Flags when a toy README line contradicts the board or register, and points at toy-tidy rather than fixing inline. - Use Case: When Chris asks "where are the toys at" before planning what to build next, produce a one-glance table of every toy's stage, board state, latest feedback, and open jams, plus three lines on what is actually moving this week. ## Quick Start Ask for the current toy status of the Lia Tools line and receive a chat table built from live board, register, and vault sources.

Frequently Asked Questions about toy-status

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

FAQPage Schema
How do I get a status overview of the Lia Tools toys?▼

Ask for the toy status or state of the line and the Skill reads live sources: the release register for stage and version, Linear for board counts, the newest feedback file, and open jam items. It returns one table with a row per toy plus the toolbox.

What sources does the toy status report read from?▼

It reads the toy_releases register in the lia Supabase project, the Linear board for the Lia Tools project, each toy's 04 build/feedback folder, meeting notes for open jam items, and toy README lines. The register wins over any document when they disagree.

What happens if Linear or the release register is unreachable?▼

The Skill reports "unreadable from here" for that column instead of guessing. It never invents a Linear status, version, or stage, treating an honest gap as better than a fabricated status.

Does the toy status skill write anything to the vault?▼

No, it is read-only and writes nothing to the vault. If the sweep surfaces drift such as a README contradicting the board, it names the drift once and points at the toy-tidy skill rather than fixing it inline.

Can the status report be posted to Slack or rendered as a dashboard?▼

Only if explicitly asked. The default output is a chat answer; on request it can produce a draft-first #toys Slack post with summary in channel and detail in thread, or a small HTML dashboard.