ark-issues
Skill438 starsChanged 7 months agoApache-2.0View on GitHub
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.
In this repository29 other files it gives its agents.
- ark/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- a2a-protocolSkill
- Ark AnalysisSkill
- ark-architectureSkill
- ark-controller-developmentSkill
- ark-dependabot-managementSkill
- ark-sdk-developmentSkill
- ark-setup-clusterSkill
- ark-chainsaw-testingSkill
- Ark Dashboard and UI TestingSkill
- ark-documentationSkill
- issue-creationSkill
- multi-branch-cluster-setupSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- ark-pentest-issue-resolverSkill
- ark-researchSkill
- slack-announcementSkill
- ark-vulnerability-fixerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 10 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when:
- Distinctive: line 20
Search for existing CVE-related issues before starting work
- Distinctive: line 22
Create new issues for tracking discovered vulnerabilities
- Very specific: line 26
Use the gh CLI tool for all issue operations:
- Distinctive: line 111
Before creating a new security fix, check if an issue already exists:
- Very specific: line 121
Tip: When creating PRs, reference the issue number using Closes #123 in the PR body to automatically close the issue when the PR merges.
- Distinctive: line 165
Always search first: Check if a similar issue already exists
- Distinctive: line 170
Be specific: Use clear, descriptive titles
- Very specific: line 178
Use Closes #123 or Fixes #123 in PR descriptions to auto-close issues
- Distinctive: line 180
Use issue numbers in commit messages for traceability
- Distinctive: line 228
If you hit GitHub API rate limits:
- Distinctive: line 229
Wait a few minutes before retrying
- Very specific: line 230
Use gh auth status to check your rate limit status
- Distinctive: line 237
Search for existing CVE issues: before starting work:
- Very specific: line 265
Repository: All commands target mckinsey/agents-at-scale-ark
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ark Issues
Manage GitHub issues for the Ark project (mckinsey/agents-at-scale-ark).
When to use this skill
Use this skill when:
- Searching for existing issues by keyword or CVE number
- Finding issues related to security vulnerabilities
- Creating new issues to track bugs or features
- Viewing issue details and status
- Listing open or closed issues
Note: This skill is commonly used by the ark-security-patcher agent to:
- Search for existing CVE-related issues before starting work
- Link PRs to existing issues with "Closes #N" syntax
- Create new issues for tracking discovered vulnerabilities
GitHub CLI Commands
Use the gh CLI tool for all issue operations:
Searching Issues
# Search issues by keyword
gh search issues --repo mckinsey/agents-at-scale-ark "CVE"
# Search for specific CVE numbers
gh search issues --repo mckinsey/agents-at-scale-ark "CVE-2025-55183"
# Search with filters
gh search issues --repo mckinsey/agents-at-scale-ark "security" --state open
gh search issues --repo mckinsey/agents-at-scale-ark "vulnerability" --label securityListing Issues
# List all open issues
gh issue list --repo mckinsey/agents-at-scale-ark
# List issues with filters
gh issue list --repo mckinsey/agents-at-scale-ark --state open
gh issue list --repo mckinsey/agents-at-scale-ark --label bug
gh issue list --repo mckinsey/agents-at-scale-ark --assignee @me
# List with custom fields
gh issue list --repo mckinsey/agents-at-scale-ark --json number,title,state,labelsViewing Issue Details
# View specific issue
gh issue view 123 --repo mckinsey/agents-at-scale-ark
# View with comments
gh issue view 123 --repo mckinsey/agents-at-scale-ark --comments
# View as JSON for parsing
gh issue view 123 --repo mckinsey/agents-at-scale-ark --json number,title,body,state,labelsCreating Issues
# Create issue interactively
gh issue create --repo mckinsey/agents-at-scale-ark
# Create with title and body
gh issue create --repo mckinsey/agents-at-scale-ark \
--title "Security: Fix CVE-2025-XXXXX" \
--body "Description of the vulnerability..."
# Create with labels
gh issue create --repo mckinsey/agents-at-scale-ark \
--title "Bug: API endpoint fails" \
--body "Steps to reproduce..." \
--label bug,priority:highUpdating Issues
# Close an issue
gh issue close 123 --repo mckinsey/agents-at-scale-ark
# Reopen an issue
gh issue reopen 123 --repo mckinsey/agents-at-scale-ark
# Add comment
gh issue comment 123 --repo mckinsey/agents-at-scale-ark \
--body "Fixed in PR #456"
# Edit issue
gh issue edit 123 --repo mckinsey/agents-at-scale-ark \
--title "New title" \
--add-label securityCommon Workflows
Workflow 1: Check for Existing CVE Issues
Before creating a new security fix, check if an issue already exists:
# Search for CVE number
gh search issues --repo mckinsey/agents-at-scale-ark "CVE-2025-55183"
# If found, note the issue number
# If not found, you may want to create oneTip: When creating PRs, reference the issue number using Closes #123 in the PR body to automatically close the issue when the PR merges.
Workflow 2: Find All Security-Related Issues
# Search by keyword
gh search issues --repo mckinsey/agents-at-scale-ark "security OR vulnerability OR CVE"
# Filter by label if security labels exist
gh issue list --repo mckinsey/agents-at-scale-ark --label securityWorkflow 3: Create Security Issue for Tracking
gh issue create --repo mckinsey/agents-at-scale-ark \
--title "fix: CVE-2025-XXXXX in [component]" \
--body "$(cat <<'EOF'
## Vulnerability Details
- **CVE**: CVE-2025-XXXXX
- **Severity**: High
- **Component**: [package name]
## Description
[What the vulnerability is]
## Impact on Ark
[How it affects Ark]
## Proposed Fix
[Update package to version X.Y.Z]
## References
- CVE: https://cve.circl.lu/cve/CVE-2025-XXXXX
- Advisory: [URL]
EOF
)" \
--label securityBest Practices
Before Creating Issues
- Always search first: Check if a similar issue already exists
gh search issues --repo mckinsey/agents-at-scale-ark "keyword" - Be specific: Use clear, descriptive titles
- Good: "fix: CVE-2025-55183 in Next.js affects dashboard"
- Bad: "security issue"
- Include context: Provide all relevant details in the issue body
When Linking Issues to PRs
- Use
Closes #123orFixes #123in PR descriptions to auto-close issues - Reference multiple issues:
Closes #123, Closes #456 - Use issue numbers in commit messages for traceability
Issue Formatting
For security issues, use this template:
## Vulnerability Details
- **CVE**: CVE-YYYY-NNNNN
- **Severity**: [Critical/High/Medium/Low]
- **Component**: [Package/library name]
## Description
[Clear explanation of the vulnerability]
## Impact on Ark
[Which services are affected and how]
## Proposed Fix
[Recommended mitigation approach]
## References
- CVE: [URL]
- Advisory: [URL]Error Handling
Issue Not Found
gh issue view 999 --repo mckinsey/agents-at-scale-ark
# Error: issue not foundSolution: Verify the issue number is correct
Permission Denied
gh issue create --repo mckinsey/agents-at-scale-ark
# Error: permission deniedSolution: Ensure you're authenticated with gh auth status and have write access to the repo
Rate Limiting
If you hit GitHub API rate limits:
- Wait a few minutes before retrying
- Use
gh auth statusto check your rate limit status - Consider batching operations
Integration with Security Workflow
The ark-security-patcher agent uses this skill to:
- Search for existing CVE issues before starting work:
gh search issues --repo mckinsey/agents-at-scale-ark "CVE-2025-55183" - Link PRs to issues by including in PR body:
Closes #33 - Track vulnerability fixes by creating issues when CVEs are discovered
Example workflow:
# Agent searches for CVE issue
ISSUE=$(gh search issues --repo mckinsey/agents-at-scale-ark "CVE-2025-55183" --json number --jq '.[0].number')
if [ -n "$ISSUE" ]; then
echo "Found existing issue #$ISSUE"
# Include "Closes #$ISSUE" in PR
else
echo "No existing issue found"
# Optionally create a new issue
fiImportant Notes
- Repository: All commands target
mckinsey/agents-at-scale-ark - Authentication: Requires
ghCLI to be authenticated (gh auth login) - Permissions: Need read access to search/view, write access to create/update
- Rate limits: GitHub API has rate limits; be mindful of excessive searches
Common Patterns
Parse JSON Output
# Get issue numbers matching a search
gh search issues --repo mckinsey/agents-at-scale-ark "CVE" \
--json number,title --jq '.[] | "\(.number): \(.title)"'
# Check if issue exists
EXISTS=$(gh search issues --repo mckinsey/agents-at-scale-ark "CVE-2025-55183" --json number --jq 'length')
if [ "$EXISTS" -gt 0 ]; then
echo "Issue exists"
fiBatch Operations
# List all open security issues
gh issue list --repo mckinsey/agents-at-scale-ark \
--label security --state open \
--json number,title --jq '.[] | "\(.number): \(.title)"'
# Create multiple issues from a list
for cve in CVE-2025-001 CVE-2025-002; do
gh issue create --repo mckinsey/agents-at-scale-ark \
--title "Security: Fix $cve" \
--body "Track fix for $cve"
doneDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

