triaging-issues

Covers this repository's issue vocabulary: the labels in .github/labels.yml, what `blocked: design`, `blocked: dependency`, `blocked: external`, `on hold`, and `tracking` mean, and what an issue body must contain (a `path:line`, an observable close condition, a `Depends on: #N` line). Use when filing an issue, triaging or re-prioritizing the backlog, picking a `priority: P0`-`P3` label, choosing between `bug`/`enhancement`/`documentation`/`chore`/`security`, marking a tracking issue, running `just labels`, recording a problem found outside the task, or routing a daily-use request.

What does this entry provide?

triaging-issues is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. # Triaging Issues **Owns:** this repository's issue vocabulary — the label taxonomy, what a priority means, and what an issue body must contain. **Does not own. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding triaging-issues to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.

Snapshot facts

Source: GitHub Skill Search
Quality: 58/100
Install method: codex
Repo: tomada1114/fastapi-react-template
Repo updated: Oct 23, 2026

Install command

codex skill install tomada1114/fastapi-react-template

Install method: codex

Review the upstream source before running this command.

GitHub project

Quality

Repo stars

Repo updated

Unknown

How is this score calculated?

Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.

Security signals

Scan coverage: Install metadata and the indexed document body.

Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.

Discovery note

# Triaging Issues **Owns:** this repository's issue vocabulary — the label taxonomy, what a priority means, and what an issue body must contain. **Does not own:** implementing an i

Report an issue with this listing