issue-creation

Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.

Quality

79%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/issue-creation/SKILL.md

Quality

Discovery

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has good trigger terms and completeness with an explicit 'Trigger:' clause, but lacks specificity about what concrete actions the skill performs beyond a generic 'issue creation workflow.' The distinctiveness is moderate—it names a specific system but the triggers are broad enough to potentially conflict with other GitHub-related skills.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Creates GitHub issues with structured templates, applies labels, assigns milestones, and enforces issue-first workflow requirements.'

Clarify what 'issue-first enforcement system' means in practical terms to help distinguish this skill from generic GitHub issue creation skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Issue creation workflow for Agent Teams Lite') and references a system ('issue-first enforcement system'), but does not list specific concrete actions like creating issues, assigning labels, setting priorities, or linking to projects.	2 / 3
Completeness	Explicitly answers both 'what' (issue creation workflow for Agent Teams Lite following the issue-first enforcement system) and 'when' (Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature).	3 / 3
Trigger Term Quality	Includes natural trigger terms users would say: 'creating a GitHub issue', 'reporting a bug', 'requesting a feature'. These are common, natural phrases that align well with user intent.	3 / 3
Distinctiveness Conflict Risk	The mention of 'Agent Teams Lite' and 'issue-first enforcement system' adds some specificity, but 'creating a GitHub issue' and 'reporting a bug' are fairly broad triggers that could overlap with general GitHub or project management skills.	2 / 3
	Total	10 / 12 Passed

Implementation

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with clear workflows and executable CLI examples. Its main weakness is length — the detailed template field tables and full-body CLI examples make it verbose for a SKILL.md that could serve as an overview pointing to reference material. The workflow enforcement (approval before PR) is well-communicated with clear sequencing.

Suggestions

Move the detailed template field tables and full CLI body examples into a separate reference file (e.g., ISSUE_TEMPLATES_REFERENCE.md) and keep SKILL.md as a concise overview with quick-start commands.

Remove the Decision Tree section as it restates information already covered in the 'When to Use' and template sections.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some redundancy — the decision tree repeats information already covered, the label system table partially restates what's in the template sections, and the full CLI examples with every field spelled out are quite lengthy. Some tightening is possible, though the content is mostly useful.	2 / 3
Actionability	Fully executable CLI commands with `gh issue create` examples that are copy-paste ready, complete with template names, title conventions, and body formatting. The commands section at the end provides a quick reference for all key operations.	3 / 3
Workflow Clarity	The workflow is clearly sequenced with explicit steps (search → template → fill → submit → wait for approval → PR). The maintainer approval workflow provides a clear feedback loop, and the enforcement that PRs cannot be opened without `status:approved` serves as a validation checkpoint.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and tables, but it's a long monolithic file (~150+ lines of content) that could benefit from splitting the detailed template field descriptions and full CLI examples into separate reference files, keeping SKILL.md as a concise overview.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Gentleman-Programming/agent-teams-lite
Commit: 6901875

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.