Agent skill · Audited from source
Export Open Issues
skill · huytieu/COG-second-brainMIT licenceAudited 14 Oct 2026 · source 6ea1a6ff2160
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 6ea1a6ff2160 and found no filesystem, network or shell access and no hard-coded secrets. What it does: Audit and export open issues from any project tracker with summary analysis and vault archival
Cite
Cite this page
ModelsAtlas. “Export Open Issues (huytieu/COG-second-brain)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/huytieu/export-open-issues
Trust audit
Audit 0.4.1 · source read 14 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 6ea1a6ff2160 · 14 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherhuytieu GitHub userOwner of the repository this skill is read from
- Source folderhuytieu/COG-second-brain/.claude/skills/export-open-issuesThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict6ea1a6ff2160A new audit runs when the source changes
- Repository statusNot archivedLast push 11 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: Audit and export open issues from any project tracker with summary analysis and vault archival
--- 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 ```markdown --- 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 | |---|-------|----------|----------|-----------|-------------| | [
Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 6ea1a6f
git clone https://github.com/huytieu/COG-second-brain git -C COG-second-brain checkout 6ea1a6ff2160
The author documents no install command, so this uses the repository directly. Our verdict covers commit 6ea1a6ff2160 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
6ea1a6ff2160
README badge
For maintainers · shows the latest audit
[](https://modelsatlas.com/skills/huytieu/export-open-issues/)
The badge shows our verdict and grade for this skill, and links back to this page. It changes when the audit does.
Similar skills
huytieu/COG-second-brain
Deep strategic research engine — decomposes questions into parallel research threads, spawns multiple agents, and synthesizes into actionable strategic analysis
huytieu/COG-second-brain
Quick capture of raw thoughts with intelligent domain classification and competitive intelligence extraction
huytieu/COG-second-brain
Deep-dive 7-day analysis across all data sources for weekly reviews, board prep, and strategic planning
huytieu/COG-second-brain
Create user stories with duplicate checking across any project tracker (Linear, GitHub Issues, Jira)
huytieu/COG-second-brain
Generate personalized news intelligence with verified sources (7-day freshness requirement)
huytieu/COG-second-brain
Generate product requirements documents with optional publishing to Confluence or other wiki platforms
Add this badge to your README
[](https://modelsatlas.com/skills/huytieu/export-open-issues/)
<a href="https://modelsatlas.com/skills/huytieu/export-open-issues/"><img src="https://modelsatlas.com/skills/huytieu/export-open-issues/badge.svg" alt="ModelsAtlas: SAFE B"></a>
Questions about Export Open Issues
What does the Export Open Issues skill do?
Is Export Open Issues safe to install?
What can Export Open Issues access on my machine?
How current is this page?
Sources
- github.com/huytieu/COG-second-brain/tree/main/.claude/skills/exp — the audited source at commit 6ea1a6ff2160 and every finding aboveObserved · 14 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Export Open Issues skill do?
- Is Export Open Issues safe to install?
- What can Export Open Issues access on my machine?