MemPalace Memory Search
MemPalace/mempalace
Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.
Audit and export open issues from any project tracker with summary analysis and vault archival
Install Export Open Issues
$ npx skills add huytieu/COG-second-brain --skill export-open-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install huytieu/COG-second-brain export-open-issues --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/export-open-issues .claude/skills/export-open-issues && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "export-open-issues" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/export-open-issues into .claude/skills/export-open-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "export-open-issues", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/huytieu/COG-second-brain/tree/main/skills/export-open-issuesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add huytieu/COG-second-brain --skill export-open-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install huytieu/COG-second-brain export-open-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/export-open-issues .agents/skills/export-open-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "export-open-issues" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/export-open-issues into .agents/skills/export-open-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "export-open-issues", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add huytieu/COG-second-brain --skill export-open-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install huytieu/COG-second-brain export-open-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/export-open-issues .cursor/skills/export-open-issues && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "export-open-issues" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/export-open-issues into .cursor/skills/export-open-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "export-open-issues", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/huytieu/COG-second-brain.git --path skills/export-open-issues--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add huytieu/COG-second-brain --skill export-open-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install huytieu/COG-second-brain export-open-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/export-open-issues .gemini/skills/export-open-issues && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "export-open-issues" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/export-open-issues into .gemini/skills/export-open-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "export-open-issues", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install huytieu/COG-second-brain export-open-issuesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add huytieu/COG-second-brain --skill export-open-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/export-open-issues .github/skills/export-open-issues && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "export-open-issues" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/export-open-issues into .github/skills/export-open-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "export-open-issues", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add huytieu/COG-second-brain --skill export-open-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install huytieu/COG-second-brain export-open-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/export-open-issues .opencode/skills/export-open-issues && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "export-open-issues" agent skill from https://github.com/huytieu/COG-second-brain/tree/main/skills/export-open-issues into .opencode/skills/export-open-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "export-open-issues", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
export-open-issues- GitHub stars
- 1.3k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 444 words
- Files
- 1
- Skills in repo
- 37
- Repo updated
- First seen
- Licence
- MIT
At a glance
Audit and export open issues from any project tracker with summary analysis and vault archival
- Works in 5 steps: Collect Open Issues → Analyze and Categorize → Generate Report → …
- Agent Workflows work in your project
- SKILL.md covers When to Invoke, Agent Mode Awareness, Command: /export-open-issues and Pre-Flight Check, plus 4 more sections
- Calls gh
What it does
Export Open Issues is an agent skill from huytieu/COG-second-brain. Audit and export open issues from any project tracker with summary analysis and vault archival
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: Self-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework… The licence is MIT.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/export-open-issues”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 36ac9d7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Export Open Issues loads about 2.2k tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 444 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from huytieu/COG-second-brain at commit 36ac9d7, republished under its MIT licence (© huytieu). 444 words, ~2,174 tokens.
Download SKILL.mdSave it as
.claude/skills/export-open-issues/SKILL.md (or your agent's skills folder).- 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
Read
00-inbox/MY-INTEGRATIONS.mdto determine which trackers are activeRead
00-inbox/MY-PROFILE.mdfor active projectsGet current timestamp: Run
date '+%Y-%m-%d %H:%M'using BashAsk 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 fieldsAgent: "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 metadataAgent: "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 metadataSolo 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"Show full SKILL.md (175 more words)Show less
Phase 5: Present Results
Show the user:
- Executive summary
- Key health alerts (stale, blocked, unassigned)
- Top recommendations
- 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
© huytieu, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/export-open-issues of huytieu/COG-second-brain.
Open the folder on GitHubat commit 36ac9d7
Compare with similar skills
Export Open Issues next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Export Open Issues this skillhuytieu/COG-second-brain | 1.3k | — | ~2.2k | Automated safety check: Pass | MIT | |
| MemPalace Memory SearchMemPalace/mempalace | 59k | — | ~1.4k | Automated safety check: Pass | MIT | |
| MemPalace Setup and OperationMemPalace/mempalace | 59k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Qmdbreferrari/obsidian-mind | 4.9k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Aiception Skill ExtractionNateBJones-Projects/OB1 | 4.7k | — | ~2k | Automated safety check: Notes | Custom licence | |
| Using LWC Memory and Graphssickn33/agentic-awesome-skills | 47k | 1 repos | ~2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
MemPalace Setup and Operation
MemPalace/mempalace
Installs and configures MemPalace as a private local palace, a shared-brain hub or a client of an existing hub, including MCP registration and version-correct initialization.
Qmd
breferrari/obsidian-mind
Search the vault using QMD semantic search. An agent skill from breferrari/obsidian-mind.
Aiception Skill Extraction
NateBJones-Projects/OB1
Pulls reusable knowledge out of work sessions and turns it into new skills, checking existing notes and skills first to avoid duplicates.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Documentation Server
andrea9293/mcp-documentation-server
A skill your agent uses when you need to store, retrieve, search, or manage documents in a local knowledge base with semantic search and hybrid (vector + full-text) retrieval.
More from huytieu/COG-second-brain
All 37 skills in this repoVoice Baseline
huytieu/COG-second-brain
Measure your own writing corpus for the words and sentence shapes you over-use, so an agent writing in your voice stops amplifying your tics into a style.
Daily Journal
huytieu/COG-second-brain
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.
Editorial Illustrations
huytieu/COG-second-brain
Generate meaning-carrying editorial data-illustrations in the monotykamary / Linear aesthetic (near-black grayscale, Inter display + mono labels, hairline framed figures) with a single coral accent.
Loop Engineering
huytieu/COG-second-brain
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns.
Knowledge Consolidation
huytieu/COG-second-brain
Build frameworks from scattered insights across all braindumps and notes
Release Video
huytieu/COG-second-brain
Turn a product release (the list of shipped items plus real screen recordings) into a motion recap video and one explained demo per feature, with sound effects tied to on-screen motion and a…
Related
Categories
Questions about Export Open Issues
What does Export Open Issues do?
Audit and export open issues from any project tracker with summary analysis and vault archival. Export Open Issues is an agent skill from huytieu/COG-second-brain.
When should I use Export Open Issues?
Export Open Issues fits situations like: agent Workflows work in your project.
How do I install Export Open Issues in Claude Code?
Run `npx skills add huytieu/COG-second-brain --skill export-open-issues -a claude-code`. Or copy the skill folder (skills/export-open-issues in huytieu/COG-second-brain) into .claude/skills/export-open-issues in your project. Claude Code loads it when a task matches its description.
How do I install Export Open Issues in Codex?
Run `npx skills add huytieu/COG-second-brain --skill export-open-issues -a codex`. Or copy the skill folder (skills/export-open-issues in huytieu/COG-second-brain) into .agents/skills/export-open-issues in your project. Codex loads it when a task matches its description.
Can I use Export Open Issues in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add huytieu/COG-second-brain --skill export-open-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/export-open-issues, .gemini/skills/export-open-issues, .github/skills/export-open-issues and .opencode/skills/export-open-issues in your project.
What does Export Open Issues need to run?
Going by SKILL.md and its folder, Export Open Issues needs the command-line tools its instructions call (gh).
Does Export Open Issues access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Export Open Issues safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Export Open Issues use?
Export Open Issues is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Export Open Issues use?
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Export Open Issues?
Skills that share tags, products or a category with Export Open Issues: MemPalace Memory Search (MemPalace/mempalace, 59k stars), MemPalace Setup and Operation (MemPalace/mempalace, 59k stars), Qmd (breferrari/obsidian-mind, 4.9k stars) and Aiception Skill Extraction (NateBJones-Projects/OB1, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Export Open Issues?
huytieu (a GitHub user) maintains it in huytieu/COG-second-brain, which has 1,265 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 2, 2026.
Source: huytieu/COG-second-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.