label-taxonomy

Fetch Gitea organization and repository label taxonomies for issue classification.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill label-taxonomy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: label-taxonomy
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/projman/skills/label-taxonomy
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill label-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a dynamic, centralized reference for Gitea label taxonomy, ensuring labels are consistently used across organization and repository scopes and never hardcoded.

Core Features & Use Cases

  • Dynamic taxonomy fetching: Reads current organization and repository labels from Gitea to guide issue classification.
  • Consistent labeling: Helps teams standardize labels across projects and repos to improve search and reporting.
  • Use Case: When triaging issues, the system can reference up-to-date taxonomy to categorize new issues automatically.

Quick Start

Activate the label-taxonomy skill to load the latest Gitea label taxonomy into context for reference.

Frequently Asked Questions about label-taxonomy

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

FAQPage Schema
How do I fetch Gitea labels dynamically for issue classification in multi-repo projects?

To fetch Gitea labels dynamically for issue classification, activate the label-taxonomy skill to load current organization and repository label groups into context. This prevents hardcoding labels and ensures consistent taxonomy across multi-repo projects.

What is a dynamic Gitea label taxonomy and when do I need it for repository labels?

A dynamic Gitea label taxonomy is a centralized, up-to-date reference of organization and repository labels. You need it when triaging issues in multi-repo projects to standardize labeling, improve search, and support consistent reporting without hardcoding.

Can I apply consistent organization labels and repository labels across different Gitea scopes?

Yes, you can apply consistent organization and repository labels across different Gitea scopes. The taxonomy reference fetches current labels dynamically from both scopes, ensuring standardized issue labeling and classification throughout your projects.

How do I standardize issue labels across Gitea repositories to improve search and reporting?

To standardize issue labels across Gitea repositories, load the dynamic taxonomy reference to guide categorization. This ensures all repos use consistent organization and repository labels, which improves search accuracy and reporting capabilities.

Why avoid hardcoding Gitea labels when categorizing issues in multi-repo projects?

You should avoid hardcoding Gitea labels because hardcoded values become outdated when taxonomy changes. Fetching dynamic label references ensures the system uses current organization and repository labels for accurate issue classification.