archon-triage

Apply type, effort, priority, and area labels to GitHub issues.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI --skill archon-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archon-triage
Source: https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI/tree/main/payload/claw-code/.claw/skills/archon-triage
Command: npx skills add https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI --skill archon-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage GitHub issues by applying type, effort, priority, and area labels in an isolated context to keep main conversations clean.

Core Features & Use Cases

  • Triage issues automatically by applying a complete label set (type, effort, priority, area) to keep issues organized.
  • Runs in an isolated forked context to prevent polluting the main conversation with issue details.
  • Validates label completeness using a prompt hook before applying changes to GitHub.

Quick Start

Tell archon-triage to triage issue numbers by applying a full set of labels with a single command.

Frequently Asked Questions about archon-triage

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

FAQPage Schema
How do I automatically apply GitHub issue labels for triage?

GitHub issue triage is automated by applying type, effort, priority, and area labels to open issues. The process runs in an isolated forked context and validates label completeness via a prompt hook before committing edits to the repository.

What are type, effort, priority, and area labels in GitHub issue management?

GitHub issue management labels categorize open issues across four dimensions: type, effort, priority, and area. These categories are validated for completeness before any changes are applied, ensuring issues receive a full and consistent label set.

Can I triage a range of GitHub issues at once instead of one by one?

Triage supports both single-issue and range operations for open GitHub issues. You can apply the complete label set across a specified range of issue numbers with a single command, keeping the main conversation clean via an isolated forked context.

Does GitHub issue triage work in an isolated context to keep conversations clean?

GitHub issue triage runs in an isolated forked context to prevent polluting the main conversation with repository details. It uses a restricted agent with Bash, Read, Glob, and Grep tools to evaluate and apply labels safely.

Why does my GitHub triage agent need to validate labels before applying edits?

Validating labels before GitHub edits ensures all four label categories—type, effort, priority, and area—exist prior to modification. A prompt hook enforces this completeness, preventing incomplete or misapplied label coverage on open issues.