ark-issues
Search, list, view, and update existing GitHub issues. Primary use case is CVE tracking and security vulnerability issue management. Used by the ark-security-patcher agent. For drafting NEW issues with research and task breakdowns, use the "issue-creation" skill instead.
80
71%
Does it follow best practices?
Impact
94%
1.40xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/issues/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly specifies concrete actions (search, list, view, update), a well-defined domain (CVE tracking and security vulnerability issue management on GitHub), and explicit boundary guidance distinguishing it from the related 'issue-creation' skill. The description is concise, uses third person voice, and includes natural trigger terms that would help Claude correctly select this skill.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Search, list, view, and update existing GitHub issues.' Also specifies the primary use case domain: 'CVE tracking and security vulnerability issue management.' | 3 / 3 |
Completeness | Clearly answers 'what' (search, list, view, update GitHub issues for CVE/security tracking) and 'when' (used by ark-security-patcher agent, for existing issues). Also explicitly distinguishes from the 'issue-creation' skill, providing clear boundary guidance on when NOT to use it. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'GitHub issues', 'CVE tracking', 'security vulnerability', 'issue management', 'search', 'list', 'view', 'update'. These are terms a user or agent would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: existing GitHub issues for CVE/security vulnerability tracking. Explicitly differentiates from the 'issue-creation' skill, reducing conflict risk. The mention of 'ark-security-patcher agent' and 'existing' issues creates a very clear boundary. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable `gh` CLI commands covering a comprehensive range of issue management operations. However, it is severely bloated with repetition (the repo flag appears ~30 times, the security template appears twice, and multiple sections overlap significantly). The content would benefit enormously from establishing the repo as a default/variable, splitting advanced patterns into separate files, and eliminating redundant sections.
Suggestions
Define the repo once at the top (e.g., 'All commands below assume `--repo mckinsey/agents-at-scale-ark`') and remove it from every individual command to dramatically reduce token count.
Eliminate duplicate content: the security issue template appears twice, and the 'Integration with Security Workflow' section largely repeats 'Common Workflows' — consolidate into one section.
Move advanced patterns (JSON parsing, batch operations, error handling) into a separate reference file and link to it from the main skill.
Remove explanations Claude already knows (e.g., 'Solution: Verify the issue number is correct', what 'Closes #123' syntax does) to further reduce verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and repetitive. The `--repo mckinsey/agents-at-scale-ark` flag is repeated in every single command (~30 times) when it could be stated once. The 'Integration with Security Workflow' section largely duplicates 'Common Workflows'. The 'When to use this skill' section, 'Important Notes', and 'Best Practices' all repeat information. The security issue template appears twice. Claude doesn't need explanations like 'Solution: Verify the issue number is correct'. | 1 / 3 |
Actionability | All commands are fully executable, copy-paste ready `gh` CLI commands with concrete flags, JSON output parsing with `jq`, and real-world examples including bash scripting patterns for conditional logic. The security issue creation template with heredoc is particularly well-formed. | 3 / 3 |
Workflow Clarity | Workflows are listed and sequenced, but the 'Check for Existing CVE Issues' workflow lacks explicit validation/verification steps. The batch operations section at the end has no validation or error handling for the loop. The search-then-create workflow is clear but could benefit from explicit checkpoints for confirming results before proceeding. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text (~200 lines) with no references to external files. Content like the full security issue template, batch operation patterns, JSON parsing examples, and error handling could be split into separate reference files. Everything is inlined, making it hard to navigate and consuming excessive context window. | 1 / 3 |
Total | 7 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- mckinsey/agents-at-scale-ark
- Commit
fc5746e
- 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.