SkillAgentSearch skills...

export-open-issues

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

Install / Use

npx skills add huytieu/COG-second-brain --skill export-open-issues

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Our assessment of export-open-issues

export-open-issues scores 89/100 on our quality scale, 27th of 82 Project & Program Management skills we index (top 33%).

Its SKILL.md is 8.5 KB long, well organised into 34 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.

With 1,216 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
12/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so export-open-issues is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

export-open-issues compared with similar skills

All 4 of these similar skills score higher than export-open-issues; compare them before choosing.

SkillScoreStarsUpdatedFormat
export-open-issues (this skill)by huytieu891.2k59d agoSKILL.md
Agent-Reachby Panniantong100112.3k9d agoCLAUDE.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install export-open-issues?
Run npx skills add huytieu/COG-second-brain --skill export-open-issues. The install tabs above show the steps for each supported agent.
Which AI agents does export-open-issues work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is export-open-issues safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is export-open-issues still maintained?
The repository was last updated about 2 months ago, so export-open-issues is actively maintained.

name: export-open-issues description: Audit and export open issues from any project tracker with summary analysis and vault archival roles: [product-manager, engineering-lead, founder] integrations: [github, linear, jira]

COG Export Open Issues Skill

When to Invoke

  • User wants to audit open issues or backlog health
  • User says "export issues", "open issues", "backlog audit", "issue report", "what's open"
  • Sprint/cycle planning prep — need a clear picture of what's in flight
  • Stakeholder reporting — need a snapshot of current work status

Agent Mode Awareness

Check agent_mode in 00-inbox/MY-PROFILE.md frontmatter:

  • If agent_mode: team — use parallel agents to collect from all active trackers simultaneously and produce a unified report
  • If agent_mode: solo — collect from the primary tracker sequentially

Command: /export-open-issues

Pre-Flight Check

  1. Read 00-inbox/MY-INTEGRATIONS.md to determine which trackers are active

  2. Read 00-inbox/MY-PROFILE.md for active projects

  3. Get current timestamp: Run date '+%Y-%m-%d %H:%M' using Bash

  4. Ask the user (if not already provided):

    • Which project? (if multiple active)
    • Scope: all open issues, or filtered by label/milestone/assignee?
    • Include additional analysis? (aging, priority distribution, assignee load)

Execution Strategy

Phase 1: Collect Open Issues

Team Mode (parallel agents)

Launch collection agents using the Task tool with run_in_background: true:

Agent: "github-issues-collector" (if GitHub is active)

Export all open issues from GitHub.
Repository: [CUSTOMIZE: your-org/your-repo]

1. Get all open issues:
   gh issue list --repo [CUSTOMIZE: your-org/your-repo] --state open --json number,title,author,assignees,labels,createdAt,updatedAt,milestone,url --limit 500

2. Get all open PRs (separate from issues):
   gh pr list --repo [CUSTOMIZE: your-org/your-repo] --state open --json number,title,author,labels,createdAt,updatedAt,reviewDecision,url --limit 200

For each issue, calculate:
- Age in days (today - createdAt)
- Days since last update (today - updatedAt)
- Staleness flag: >30 days since last update = stale

Return: full issue list with calculated fields

Agent: "linear-issues-collector" (if Linear is active)

Export all open issues from Linear.

1. Use ToolSearch to load Linear tools
2. List all teams: mcp__claude_ai_Linear_2__list_teams
3. For each relevant team, list open issues: mcp__claude_ai_Linear_2__list_issues
4. Get current cycles: mcp__claude_ai_Linear_2__list_cycles
5. Get milestones: mcp__claude_ai_Linear_2__list_milestones

For each issue, collect:
- ID, title, status, priority, assignee, labels, project
- Created date, updated date
- Cycle membership
- Blocked status

Return: full issue list with metadata

Agent: "jira-issues-collector" (if Jira is active)

Export all open issues from Jira.
Project: [CUSTOMIZE: YOUR-PROJECT-KEY]

1. Search open issues:
   JQL: project = "[CUSTOMIZE: YOUR-PROJECT-KEY]" AND status NOT IN (Done, Closed, Resolved) ORDER BY priority DESC, created ASC

2. For each issue, collect:
   key, summary, issuetype, status, priority, assignee, reporter, labels, components, fixVersion, created, updated, duedate

Return: full issue list with metadata

Solo Mode

Run collection sequentially for the primary tracker.

Phase 2: Analyze and Categorize

Process the collected data to produce:

2.1 Summary Statistics

Total Open Issues: [N]
  - By Priority: Critical [N], High [N], Medium [N], Low [N], None [N]
  - By Type: Feature [N], Bug [N], Task [N], Other [N]
  - By Status: To Do [N], In Progress [N], In Review [N], Blocked [N]
  - By Assignee: [Name] ([N]), [Name] ([N]), Unassigned ([N])

2.2 Health Indicators

  • Stale issues (no update in >30 days): list with age
  • Unassigned issues: list with priority
  • Blocked issues: list with blocker details
  • Overdue issues (past due date): list with days overdue
  • Oldest open issues: top 10 by age
  • In-progress bottleneck: issues in "In Progress" for >7 days

2.3 Distribution Charts (text-based)

Priority Distribution:
  Critical  ████░░░░░░  12%
  High      ████████░░  38%
  Medium    ██████░░░░  28%
  Low       ████░░░░░░  22%

Age Distribution:
  <7 days   ██████████  45%
  7-30 days ██████░░░░  30%
  30-90 d   ███░░░░░░░  15%
  >90 days  ██░░░░░░░░  10%

Phase 3: Generate Report

---
type: open-issues-audit
project: [project-name]
date: [YYYY-MM-DD]
created: [YYYY-MM-DD HH:MM]
source: [github/linear/jira/multi]
tags: ["#issues-audit", "#[project-name]", "#backlog"]
summary:
  total_open: [N]
  critical: [N]
  high: [N]
  stale: [N]
  unassigned: [N]
  blocked: [N]
  oldest_days: [N]
---

# Open Issues Audit — [Project Name]

**Date:** [YYYY-MM-DD]
**Source:** [Tracker(s) used]
**Total Open Issues:** [N]

---

## Executive Summary

[2-3 sentences: overall backlog health, biggest concerns, and recommended actions]

---

## Summary Statistics

| Category | Count | % of Total |
|----------|-------|-----------|
| **By Priority** | | |
| Critical | [N] | [%] |
| High | [N] | [%] |
| Medium | [N] | [%] |
| Low | [N] | [%] |
| No Priority | [N] | [%] |
| **By Status** | | |
| To Do | [N] | [%] |
| In Progress | [N] | [%] |
| In Review | [N] | [%] |
| Blocked | [N] | [%] |
| **By Type** | | |
| Feature/Story | [N] | [%] |
| Bug | [N] | [%] |
| Task | [N] | [%] |
| Other | [N] | [%] |

---

## Assignee Load

| Assignee | Open Issues | Critical/High | In Progress | Oldest Issue (days) |
|----------|-------------|---------------|-------------|-------------------|
| [Name] | [N] | [N] | [N] | [N] |
| [Name] | [N] | [N] | [N] | [N] |
| Unassigned | [N] | [N] | — | [N] |

---

## Health Alerts

### Stale Issues (>30 days without update)
| # | Title | Assignee | Priority | Age (days) | Last Updated |
|---|-------|----------|----------|-----------|-------------|
| [#] | [Title] | [Name] | [Priority] | [N] | [Date] |

### Blocked Issues
| # | Title | Assignee | Blocked By | Days Blocked |
|---|-------|----------|-----------|-------------|
| [#] | [Title] | [Name] | [Reason] | [N] |

### Unassigned High-Priority Issues
| # | Title | Priority | Age (days) | Labels |
|---|-------|----------|-----------|--------|
| [#] | [Title] | [Priority] | [N] | [Labels] |

### Overdue Issues
| # | Title | Assignee | Due Date | Days Overdue |
|---|-------|----------|----------|-------------|
| [#] | [Title] | [Name] | [Date] | [N] |

---

## Full Issue List

### Critical Priority
| # | Title | Status | Assignee | Age | Labels | URL |
|---|-------|--------|----------|-----|--------|-----|
| [#] | [Title] | [Status] | [Name] | [N]d | [Labels] | [URL] |

### High Priority
[Same table format]

### Medium Priority
[Same table format]

### Low Priority
[Same table format]

---

## Recommendations

1. **[Recommendation 1]** — [Specific action with rationale]
2. **[Recommendation 2]** — [Specific action with rationale]
3. **[Recommendation 3]** — [Specific action with rationale]

---

*Generated by COG Open Issues Audit | [Date]*

Phase 4: Save to Vault

Save to: 04-projects/[project]/audits/open-issues-YYYY-MM-DD.md

mkdir -p "04-projects/[project]/audits"

Phase 5: Present Results

Show the user:

  1. Executive summary
  2. Key health alerts (stale, blocked, unassigned)
  3. Top recommendations
  4. File location

Ask if they want:

  • Full detailed view
  • Export as CSV (generate a simple CSV file alongside the markdown)
  • Share to a specific channel or wiki

CSV Export (Optional)

If user requests CSV, generate alongside the markdown:

#,Title,Type,Status,Priority,Assignee,Labels,Created,Updated,Age(days),URL
[data rows]

Save to: 04-projects/[project]/audits/open-issues-YYYY-MM-DD.csv


Fallback Behavior

| Scenario | Behavior | |----------|----------| | No tracker active | Inform user that a project tracker integration is needed; offer to set one up | | Tracker API fails | Retry once, then report partial results with error note | | Too many issues (>500) | Paginate collection, warn user, offer to filter by label/milestone/assignee | | Multiple trackers active | Collect from all and produce a unified report, noting the source for each item | | No open issues found | Report clean backlog status (this is good news!) |

Error Handling

  • Rate limits: Paginate requests and add delays if needed
  • Large payloads: Summarize rather than list all items if >200 issues
  • Missing fields: Mark as "N/A" rather than failing
  • Context overflow: Process in batches, summarize per batch

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryProject
Updated1mo ago
Forks144

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions