Srib triage

Skill sayonsom/srib-godot-skills-demo/.claude/skills/srib-triage

Standalone proof that six Claude Code skills develop a Godot 4.6 feature end-to-end: from an Excel backlog to a runnable SmartThings home view (shaders, animation, UI, integration). Includes one-step Linux/Windows setup.

Install

npx -y skills add sayonsom/srib-godot-skills-demo --skill srib-triage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Front-door triage skill for the SRIB Godot 4.6 Android / 3D SmartThings home view project. Takes a list of feature requests, classifies each as a view (shaders/visuals), model (math/animation/simulation), integration (wiring/Android bridge/signal routing), or design (UX/layout/theming) concern, and routes each to the matching feature-level skill — srib-view, srib-model, srib-integration, or srib-design. Use whenever the user pastes a backlog, says "triage these", "classify these features", "which skill should I use for X", or hands over a batch of ambiguous feature ideas for the SRIB Android app. Note: for Excel-file intake with formal ticket creation, prefer srib-identify instead.

SKILL.md

4.5 KB, as published. Nobody here has run it

srib-triage

Project: SRIB — Godot 4.6 Android application with a 3D SmartThings home view. Role: This is the router. It does not implement anything. It reads a list of features and decides which feature-level skill should pick up each one.

Why this skill exists

SRIB feature requests usually arrive as a mixed list — some are visual, some are about how things move, some are about connecting Godot to Android/SmartThings, and some are about how the user reads and navigates the UI. Implementing them in one undifferentiated pass leads to messy diffs and bad separation of concerns.

srib-triage enforces a clean split:

Concern	Owned by	Examples
view	`srib-view`	shaders, materials, lighting, post-FX, viewport composition
model	`srib-model`	animation math, easing, tweens, physics, state machines
integration	`srib-integration`	signal wiring, SmartThings bridge, Android plugin, export/build
design	`srib-design`	layout, theming, typography, navigation, accessibility

The triage skill outputs a classification table and an execution plan, and the user then runs the right feature-level skill for each item.

When to use

User pastes a backlog or list of feature ideas.
User says: "triage these", "classify these", "what kind of feature is this".
Ambiguous request that clearly spans more than one concern.

When NOT to use

A single, already-clearly-scoped feature where the concern is obvious.
Pure bug fixes with no classification ambiguity.

Workflow

Read the list. Normalise each item to a one-line description.
Classify. For each item, assign view / model / integration / design with a confidence tag.
Split mixed-concern items. A feature like "animated glowing door that reacts to SmartThings lock state" splits into:
- view: glow shader
- model: fade-in curve
- integration: wire SmartThings lock state → model → shader param
Emit the routing table. Markdown table, one row per (sub)feature.
Emit the execution plan. Which srib-* skill to invoke in what order, what can run in parallel.

Classification cues

view — keywords: shader, material, glow, color, lighting, emissive, visual, render, post-FX, texture, opacity, outline, shadow, bloom

model — keywords: animation, curve, easing, tween, lerp, spring, physics, state machine, simulation, compute, formula, interpolation, motion

integration — keywords: wire up, connect, signal, autoload, SmartThings, Android, plugin, JNI, export, APK, bridge, route data to, drive the shader from, link, bind

design — keywords: layout, UI, typography, button, panel, screen, theme, navigation, accessibility, TalkBack, color palette, spacing, font

Output format

| # | Feature                               | Concern     | Confidence | Next skill        | Notes |
|---|---------------------------------------|-------------|------------|-------------------|-------|
| 1 | Glowing door shader                   | view        | high       | srib-view         |       |
| 2 | Door fade-in curve                    | model       | high       | srib-model        |       |
| 3 | Wire lock state → glow                | integration | high       | srib-integration  | after #1 and #2 |
| 4 | Tap feedback ripple                   | design      | medium     | srib-design       |       |

Followed by:

Execution plan
- Parallel: srib-view (#1), srib-model (#2)
- After #1 and #2: srib-integration (#3)
- Parallel with integration: srib-design (#4)

Note: for formal ticket creation from an Excel file, route to srib-identify instead.