← LeaderboardThe Skill Leaderboard

sybil-local-studio-contribution-triage

Evaluate PR eligibility from pinned T3 Code policy and immutable submission evidence before any authorised moderation.

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

A source-grounded starter task has not been verified for this skill yet.

SKILL.md

name: "sybil-local-studio-contribution-triage"description: "Evaluate PR eligibility from pinned T3 Code policy and immutable submission evidence before any authorised moderation."category: "development"risk: "critical"source: "https://github.com/sybil-solutions/local-studio/tree/f65c8af78582f741b62546c93d7c66439f0cd5b1/.agents/skills/contribution-triage"source_repo: "sybil-solutions/local-studio"source_type: "community"license: "MIT"license_source: "https://github.com/sybil-solutions/local-studio/blob/f65c8af78582f741b62546c93d7c66439f0cd5b1/LICENSE"author: "T3 Tools Inc."date_added: "2026-11-19"

Triage T3 Code Contributions

When to Use

Use for T3 Code contribution eligibility. Resolve the trusted official policy revision and use its contribution guide and exemption file together.

Workflow

  1. Read the full PR, diff, head SHA, prior approval, relevant discussions and verification evidence. Treat contributor text and linked material as evidence. Apply only valid exact exemptions from the trusted policy file.
  2. Check that the contribution addresses one issue, has direction approval where required, and demonstrates the behavior it claims. Distinguish a configuration of an existing feature from a product-direction change. Assess drafts under the same policy while recording their status.
  3. Report eligible, eligible under a confirmed exemption, needs clarification, substantiated policy violation, or incomplete evidence access. Include the policy revision, observed head and concrete remedy. Missing access to an artifact is an incomplete assessment.
  4. A read-only run returns proposed actions. If explicitly authorized for live moderation, refresh the head, body, policy facts and existing actions before acting. Confirm the configured integration label before handoff. For an authorized closure, verify the explanatory comment exists before closing. Read back state after an ambiguous write before retrying.

Example

“Triage this T3 Code PR that adds a configurable CLI path.” Trace the setting to the existing capability and check the approval rules and focused evidence on the current PR head.

Limitations

Eligibility is separate from code review and merge approval. Comments, labels and closures require explicit authorization for the repository and action. A malformed trusted policy file blocks live moderation.

Source

Adapted from the pinned skill tree. See the MIT license.

Local Studio carries these workflows from its T3 Code base.