obsfx/trekker
skills/trekker/SKILL.md
Use Trekker as the persistent source of truth for tracked work in Codex. Search first, restore context, work one task at a time, and close tasks with summary comments.
development
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add obsfx/trekker-codex trekkerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:33 PM14.6s1 file scanned
SKILL.md
- name:
- trekker
- description:
- Use Trekker as the persistent source of truth for tracked work in Codex. Search first, restore context, work one task at a time, and close tasks with summary comments.
Trekker
Overview
Use this skill when work should be tracked across sessions. Prefer the Trekker MCP tools from this plugin for structured reads and writes. If those tools are unavailable, use the trekker CLI directly.
Trekker is the durable system of record. update_plan is only short-lived session scaffolding.
Core Rules
- Search before any task action. Trekker uses FTS5, so start with one distinctive keyword at a time.
- Restore context before changing anything. Read the task, comments, history, and dependencies first.
- Keep one active task when practical. Set it to
in_progressbefore doing the work. - Leave a
Checkpoint:comment when pausing and aSummary:comment before marking work complete. - Prefer extending existing tasks over creating duplicates.
Search-First Workflow
Run search before you create, start, or resume work:
trekker search "auth"
trekker search "migration"
trekker search "release"
Multi-word queries narrow results with AND logic. If the first search is weak, try two or three adjacent keywords separately instead of writing a sentence.
Context Recovery
For existing work, inspect state in this order:
trekker task show TREK-12
trekker comment list TREK-12
trekker history --entity TREK-12
trekker dep list TREK-12
If .trekker does not exist and the user wants persistent tracking, ask before running trekker init because it changes project state.
Working a Task
trekker task update TREK-12 -s in_progress
trekker comment add TREK-12 -a "codex" -c "Checkpoint: verified the failing path in src/auth.ts. Next: patch token refresh handling."
trekker comment add TREK-12 -a "codex" -c "Summary: fixed refresh-token validation in src/auth.ts and src/session.ts. Removed the duplicate fallback branch."
trekker task update TREK-12 -s completed
trekker ready
Use comments for discoveries, blockers, and handoff context. If a task is blocked by something outside the current scope, document why and leave it in a non-terminal state or mark it wont_fix with explanation.
Planning and New Work
For larger features, create an epic first and then wire smaller tasks together with dependencies. Use update_plan only as a temporary mirror of what you are doing right now; Trekker remains the durable record.
Common Mistakes
- Creating a new task before searching.
- Marking work complete without a summary comment.
- Treating
update_planas the system of record. - Assuming Claude-only slash commands or TodoWrite behavior exist in Codex.
Related Skills
obsfx/task-sync
development
VerifiedTrustedCommunity
Keep Trekker as the source of truth while using Codex session planning as a temporary mirror.
SKILL.mdUpdated Apr 16, 2026
obsfx/task-agent
documentation
VerifiedTrustedCommunity
Work through Trekker tasks autonomously by recovering context, selecting ready work, documenting progress, and finishing with clean summaries.
SKILL.mdUpdated Apr 16, 2026
obsfx/start-task
testing
VerifiedTrustedCommunity
Start tracked work the right way: search first, restore task context, check dependencies, then mark the task in progress.
SKILL.mdUpdated Apr 16, 2026
obsfx/smart-query
databases
VerifiedTrustedCommunity
Translate natural-language tracking questions into Trekker queries for status, history, blockers, and related work.
SKILL.mdUpdated Apr 16, 2026