CtrlK
BlogDocsLog inGet started
Tessl Logo

issue-intelligence-analyst

Fetches and analyzes GitHub issues to surface recurring themes, pain patterns, and severity trends. Use when understanding a project's issue landscape, analyzing bug patterns for ideation, or summarizing what users are reporting.

68

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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.

A high-quality, highly actionable agent skill body with concrete commands, clear sequencing, and validation/checklist safeguards. The main weakness is redundancy: several critical rules are repeated across sections and could be consolidated to improve token efficiency.

Suggestions

Consolidate the "no scripts, no pipes" guidance into a single Tool Guidance section and reference it from Steps 2 and 4 instead of restating the full rule each time.

Remove the duplicate "cluster from open issues first; do not let closed issues create new themes" wording — keep it in Step 3 and trim the restatement in Step 2c.

Tighten the Output Format section by merging the field list from Step 5 with the template so each field is specified once.

DimensionReasoningScore

Conciseness

Mostly efficient actionable guidance, but key rules are restated multiple times — the "no scripts, no pipes" directive appears in Step 2 hard rules, Step 4, and a full Tool Guidance section, and "cluster from open issues first" is repeated across Step 2c and Step 3 — so it could be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready `gh` commands with exact `--jq` filters, specific JSON field lists, a concrete output template, and exact edge-case responses covering the common cases.

5 / 5

Workflow Clarity

A clearly sequenced 6-step methodology with explicit validation checkpoints (precondition checks that stop on failure) and a final output checklist for verification; the batch operation cap does not apply because validation is present.

5 / 5

Progressive Disclosure

Well-organized with clear section headers (Methodology, Steps 1-6, Output Format, Tool Guidance, Integration Points) and content appropriately placed; no bundle files exist so all content is inline, but structure keeps it navigable.

4 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description: third-person voice, concrete actions, explicit "Use when" triggers, and a distinct niche. Minor room to broaden trigger synonyms and enumerate a couple more capabilities, but it clearly answers what and when.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — "Fetches and analyzes GitHub issues", "surface recurring themes, pain patterns, and severity trends" — with only minor gaps in coverage (e.g., clustering/recurrence detection implied but not enumerated).

4 / 5

Completeness

Explicitly answers both what ("Fetches and analyzes GitHub issues to surface recurring themes...") and when ("Use when understanding a project's issue landscape, analyzing bug patterns for ideation, or summarizing what users are reporting") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("issue landscape", "analyzing bug patterns", "summarizing what users are reporting") with good coverage, though a few common synonyms (e.g., "bug reports", "pain points") are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (GitHub issue theme analysis) with distinct triggers; minimal overlap risk with adjacent code-analysis skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
udecode/plate
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.