export-open-issues

Audit and export open issues from any project tracker with summary analysis and vault archival

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The content is highly actionable with concrete executable commands and a well-sequenced five-phase workflow supported by thorough error handling. The main weaknesses are verbosity from the inline report template and the absence of any externalized reference files for a skill this size.

Suggestions

Move the Phase 3 report template (and the text-based chart examples) into a separate reference file (e.g. references/report-template.md) referenced from the body to improve both conciseness and progressive disclosure.

Add an explicit validation checkpoint between phases — e.g. verify collected issue counts and required fields before generating the report — since this is a batch operation.

Tighten the Phase 2 summary-statistics and distribution-chart blocks into compact spec-like guidance rather than fully worked examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, action-oriented operational guidance, but the inline Phase 3 report template (~100 lines) and text-based chart examples add bulk that could be condensed or externalized rather than earning every token.	2 / 3
Actionability	It provides fully executable commands throughout — concrete `gh issue list`/`gh pr list` flags, specific MCP tool names, a real JQL query, and copy-paste-ready Bash and CSV snippets — with placeholders explicitly flagged for customization.	3 / 3
Workflow Clarity	Five phases are clearly sequenced with a pre-flight checklist and a fallback/error-handling table, but for a batch collection operation the validation checkpoints between phases are implicit rather than explicit, which caps the score at 2.	2 / 3
Progressive Disclosure	The skill is a single ~300-line SKILL.md with no references/scripts/assets bundle and the large report template is inline rather than split into a separate file, matching the level-2 anchor of content that should be separate being inline despite clear sectioning.	2 / 3
	Total	9 / 12 Passed

Description

45%

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 is specific and lists concrete actions, but it omits any explicit 'Use when' trigger guidance and lacks natural user-facing keywords, which are the two areas most needed for skill discoverability. Adding a trigger clause with natural terms would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to audit open issues, run a backlog audit, or get a snapshot of what's in flight.'

Incorporate natural keywords users would actually say — 'open issues', 'backlog audit', 'issue report', 'what's open' — directly into the description rather than only the body.

Narrow 'any project tracker' toward the supported set (GitHub, Linear, Jira) to reduce overlap with unrelated project-management skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'Audit and export open issues', 'summary analysis', 'vault archival' — rather than vague language, matching the level-3 anchor of several specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 2.	2 / 3
Trigger Term Quality	The description contains no natural keywords a user would say; terms like 'any project tracker' and 'vault archival' are technical jargon, and the natural triggers ('backlog audit', 'what's open') appear only in the body, not the description.	1 / 3
Distinctiveness Conflict Risk	The action combination is fairly distinct, but the phrase 'any project tracker' is broad and could overlap with other project-management skills without the distinct trigger phrasing needed for a 3.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: huytieu/COG-second-brain
Commit: 5e9851c

Reviewed: 14 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.