CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

export-open-issues

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/export-open-issues/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

The body is commendably concise and well-structured, but it delegates all executable detail to a playbook file that is not included in the bundle, leaving actionability and workflow clarity incomplete with no validation checkpoints.

Suggestions

Either include the referenced playbook (.claude/skills/export-open-issues/SKILL.md) as a bundled reference or inline the key executable steps so the skill is self-contained.

Add explicit validation/verification steps for the export+archive flow (e.g. verify exported file is non-empty, confirm vault archival succeeded) to support a batch operation.

Ensure all referenced paths resolve to real bundled files so progressive-disclosure navigation works without external dependencies.

DimensionReasoningScore

Conciseness

The body is a lean three-line directive with no padding and no over-explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

It gives concrete file paths and a substitution rule, but the authoritative playbook it points to (.claude/skills/export-open-issues/SKILL.md) is not present in the bundle, so the actual executable steps are inaccessible.

3 / 5

Workflow Clarity

A rough sequence is present (read+execute playbook, then follow cog.md, with a substitution rule), but there are no validation/verification checkpoints for a batch export operation.

3 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the in-body references point to files outside the bundle that are not present, so navigation is incomplete despite the minimal, organized structure.

3 / 5

Total

14

/

20

Passed

Description

66%Weight 40%Scale 1-5

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 distinct, naming several concrete actions, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when...' clause with natural trigger terms would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to export or audit open issues from a project/bug tracker (e.g. Jira, Linear, GitHub Issues) and archive them.'

Include common synonyms and file extensions as trigger terms (e.g. 'bug tracker', 'CSV/JSON export') to broaden natural keyword coverage.

Tighten the action list toward a single comprehensive coverage set so specificity can reach the top anchor.

DimensionReasoningScore

Specificity

Names the domain (open issues / project tracker) and several concrete actions — 'Audit and export open issues', 'summary analysis and vault archival' — but has minor coverage gaps (no file formats or tracker-specifics) that keep it just below a 5.

4 / 5

Completeness

There is a clear 'what' (audit, export, summary analysis, vault archival) but no 'Use when...' or equivalent explicit trigger guidance, which the rubric caps at 3 for a missing when-clause.

3 / 5

Trigger Term Quality

'Audit', 'export', 'open issues', and 'project tracker' are natural phrases a user would say, but common synonyms/specific trackers (bug tracker, Jira, Linear, GitHub issues) are missing, so it is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche of auditing/exporting open issues with vault archival is mostly distinct from other skills, with only minor overlap risk against generic export skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huytieu/COG-second-brain

Path

.agents/skills/export-open-issues/SKILL.md

Reviewed

Table of Contents

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.