SkillsAdd

vincentkoc/dotskills

codex-goal-mining

Mine structured Codex /goal history locally or across a configured machine fleet, measure active goal time and resumed thread spans, identify unfinished and recurring semantic runs, and turn them into stable copy-paste rerun suites.

First seen Jul 29, 2026

Installation

$ npx skills add vincentkoc/dotskills --skill codex-goal-mining
View on skills.sh ↗ GitHub repository ↗

Summary

  • Mine structured Codex /goal history locally or across a configured machine fleet, measure active goal time and resumed thread spans, identify unfinished and recurring semantic runs, and turn them into stable copy-paste rerun suites.
  • Use when the user asks to inspect goal history, summarize goal commands, find repeated goals, recover large beta campaigns, compare goal duration or token usage, or prepare reusable /goal prompts and privacy-scrubbed reports.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from vincentkoc/dotskills · top by installs.

npx skills add vincentkoc/dotskills
technical-documentation 219 technical-integrations 91 technical-deslop 88 technical-skill-finder 78 opik-optimizer 39 opik-integrations-auditor 36 semantic-slicing 27 openclaw-github-dedupe 25 operations-worktree 7 graincrawl 6

Browse all from vincentkoc/dotskills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 102
License LICENSE
Default branch main
Open issues 4
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
Declared agents codex
More metadata
source
https://github.com/vincentkoc/dotskills

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,620 B
  • docs SUMMARY.md 483 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Codex Goal Mining

Purpose

Recover structured Codex goal history and convert free-form runs into evidence-backed, repeatable suites.

When to use

  • The user asks what /goal commands ran locally or across the fleet.
  • Large QA, beta, release, localization, model, cleanup, or PR campaigns need retesting.
  • The user wants active, paused, blocked, or long-running goals ranked.
  • Repeated semantic runs need stable suite names and copy-paste prompts.
  • Goal time, thread span, tokens, dates, machines, or reachability matter.

Workflow

  1. Collect structured data with scripts/codex-goal-report.py.

- Fleet report: scripts/codex-goal-report.py --policy ~/.config/codex-goal-mining/fleet-policy.json --json --output ~/.codex/reports/codex-fleet-goals.json - Local only: scripts/codex-goal-report.py --local --json - Recent window: add --since YYYY-MM-DD. - Selected machines: repeat --machine <fleet-alias>. - Start fleet configuration from references/fleet-policy.example.json; never commit a real private inventory.

  1. Treat the data sources correctly.

- Prefer goals1.sqlite for objective, status, tokens, and Codex-recorded active goal time. - Join state5.sqlite for thread timestamps and rollout paths. - Use JSONL only as a fallback for older installations. - Wall-clock thread span includes idle and resume gaps; never describe it as active labor.

  1. Report collection coverage first.

- List reached and unreachable machines. - Give the date range, goal count, statuses, total active goal time, and median goal time. - Preserve exact transport blockers instead of silently shrinking the fleet.

  1. Mine patterns semantically.

- Exact duplicate text is weak evidence because operators rephrase goals. - Cluster by intended test surface, matrix, exit criteria, and repeated operating contract. - Prioritize unfinished goals and recurring high-time campaigns. - Separate product beta suites from operational queues such as contributor PR sweeps.

  1. Produce reusable reruns.

- Use [suite:<name>] [baseline:<sha-or-date>] [matrix:<targets>] [exit:<criteria>]. - Include a fixed matrix, evidence requirements, blocker rules, and definition of done. - Start from references/goal-suite-patterns.md, then adapt to current evidence.

  1. Keep reports private.

- Default to ~/.codex/reports/ or another private path. - Scrub secrets, private hosts, personal absolute paths, and credentials before creating a gist or sharing externally. - Use a secret gist unless the user explicitly requests public visibility.

Inputs

  • Local Codex stores under ~/.codex/.
  • Optional fleet policy supplied with --policy or CODEXFLEETPOLICY.
  • Optional date window, machine aliases, suite focus, or output path.

Outputs

  • Markdown or JSON fleet goal report.
  • Ranked active, paused, blocked, and long-running goals.
  • Semantic campaign summary with timing and reachability caveats.
  • Stable copy-paste /goal suite prompts and rerun priority order.