CtrlK
BlogDocsLog inGet started
Tessl Logo

issue-packet

Open or file a GitHub issue, bug report, feature request, docs issue, or chore. Add evidence to an existing issue. Run gh issue create or gh issue comment.

72

Quality

87%

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

92%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 a tightly written, well-sequenced intake workflow with executable gh commands, explicit approval/validation checkpoints, and an error-recovery loop. Only minor tightening would push conciseness to the top anchor.

DimensionReasoningScore

Conciseness

Lean procedural body that assumes Claude's competence and avoids explaining concepts Claude already knows; a few sentences ('A trusted upstream file can be fetched without cloning the whole repository.') could be tightened further.

4 / 5

Actionability

Provides concrete, executable commands — 'gh issue create', 'gh issue comment' with '--title', '--label bug/enhancement/documentation/chore' and exact title prefixes — covering the common create/comment cases copy-paste ready.

5 / 5

Workflow Clarity

A clear five-step sequence with per-step completion criteria, an explicit human-approval checkpoint before posting ('Ask, then post once'), and an error-recovery loop ('If the command reports an uncertain outcome, check whether the issue or comment already exists before retrying').

5 / 5

Progressive Disclosure

A single self-contained SKILL.md under 50 lines with no external references needed, organized into five well-labeled numbered sections — meeting the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

19

/

20

Passed

Description

82%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, action-oriented, and uses natural trigger terms with low conflict risk, but it omits any explicit 'Use when' guidance, which caps completeness. Adding a trigger clause would raise the completeness score.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when the user asks to open, file, or add evidence to a GitHub issue, bug report, feature request, docs issue, or chore.') to satisfy the 'when' half of completeness.

Consider mentioning issue templates or the approval-before-posting guardrail to further distinguish this from a generic gh-CLI helper.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Open or file a GitHub issue, bug report, feature request, docs issue, or chore', 'Add evidence to an existing issue', 'Run gh issue create or gh issue comment' — covering the domain comprehensively.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Covers natural terms users say including synonyms and variants — 'GitHub issue', 'bug report', 'feature request', 'docs issue', 'chore', plus the concrete CLI triggers 'gh issue create' and 'gh issue comment'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (filing/commenting on GitHub issues via the gh CLI) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
stickerdaniel/linkedin-mcp-server
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.