{"id":42866,"plugin_id":"plugin_asdk_app_699e3e4e050881919b373090d3059dc5","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:07:35.487Z","digest":"aac166e79a7bf899e49e44e0fcacf7d7577cd9e9b6ef7d398d4008f49570b083","against":null,"payload":{"description":"Inspect and route BuildBetter Projects Hub, triage items, and Linear tickets with rich evidence, metadata discovery, and explicit promotion approval. Use when the user asks what is in triage, wants project context, needs to review linked tickets, compare product work, or promote a triage item or Linear ticket into a project.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":252}],"name":"buildbetter-project-triage","skill_md_contents":"---\nname: buildbetter-project-triage\ndescription: Inspect and route BuildBetter Projects Hub, triage items, and Linear tickets with rich evidence, metadata discovery, and explicit promotion approval. Use when the user asks what is in triage, wants project context, needs to review linked tickets, compare product work, or promote a triage item or Linear ticket into a project.\n---\n\n# BuildBetter Project Triage\n\nFollow [buildbetter-start’s interaction guidance](../buildbetter-start/SKILL.md#interaction): complete supported work through chat; use optional UI only when it reduces effort or clarifies a decision.\n\n## Safety Contract\n\nSearch organization skills with list-skills and get-skill first. Reading Projects Hub, triage, and connected ticket evidence is observational. promote-triage-item and promote-linear-tickets create project state and require explicit approval for the exact source items and target type.\n\nIf a required domain tool is unavailable, report the missing surface. Do not fall back to guessed GraphQL mutations.\n\n## Read Workflow\n\n1. Use triage-count for inbox volume and list-project-types for current type IDs, slugs, and rules.\n2. Use list-triage-items for unpromoted work and get-triage-item for rich detail: evidence, taxonomy, linked metadata, tickets, timeline, metrics, waiting-on rows, and agent sessions when present.\n3. Use list-projects for promoted work and get-project for the authoritative project_v2 detail. Keep triage item IDs, legacy tracked item IDs, and project_v2 IDs distinct.\n4. For Linear, discover filters with list-linear-teams, list-linear-projects, and list-linear-workflow-states. Then use list-linear-tickets and get-linear-ticket.\n5. Compare candidates on customer evidence, strategic fit, type, existing project coverage, linked-ticket state, owner, dependencies, and uncertainty. Do not infer priority from source system order.\n\n## Promotion Workflow\n\n1. Identify exact triage or Linear IDs, current state, proposed project type, duplicates, and already-attached items.\n2. Show a readback: source title and ID, evidence summary, selected type and ID, expected created project count, and skipped or duplicate behavior.\n3. Obtain explicit approval.\n4. Call promote-triage-item for one triage item or promote-linear-tickets for the approved Linear external IDs.\n5. Read the result. Treat returned projectId values as project_v2 IDs; legacy trackedItemId may be an alias.\n6. Verify with get-project and report created, skipped, failed, or ambiguous results exactly.\n\n## Output\n\nReport scope and filters, counts, item or project IDs, evidence, linked-ticket state, recommended next action, approval state, promotion receipt, created project IDs, skipped items, and verification. A recommendation is not a promotion.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}