Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
Implementation tracking documents for maintaining living records of what was built, what is pending, what failed, and what dead ends were explored.
$ npx skills add hashgraph-online/awesome-codex-plugins --skill impl-tracking -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins impl-tracking --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/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/JuliusBrussee/blueprint/skills/impl-tracking .claude/skills/impl-tracking && 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 "impl-tracking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/JuliusBrussee/blueprint/skills/impl-tracking into .claude/skills/impl-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "impl-tracking", 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/hashgraph-online/awesome-codex-plugins/tree/main/plugins/JuliusBrussee/blueprint/skills/impl-trackingType 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 hashgraph-online/awesome-codex-plugins --skill impl-tracking -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins impl-tracking --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/JuliusBrussee/blueprint/skills/impl-tracking .agents/skills/impl-tracking && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "impl-tracking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/JuliusBrussee/blueprint/skills/impl-tracking into .agents/skills/impl-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "impl-tracking", 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 hashgraph-online/awesome-codex-plugins --skill impl-tracking -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins impl-tracking --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/JuliusBrussee/blueprint/skills/impl-tracking .cursor/skills/impl-tracking && 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 "impl-tracking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/JuliusBrussee/blueprint/skills/impl-tracking into .cursor/skills/impl-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "impl-tracking", 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/hashgraph-online/awesome-codex-plugins.git --path plugins/JuliusBrussee/blueprint/skills/impl-tracking--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 hashgraph-online/awesome-codex-plugins --skill impl-tracking -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins impl-tracking --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/JuliusBrussee/blueprint/skills/impl-tracking .gemini/skills/impl-tracking && 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 "impl-tracking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/JuliusBrussee/blueprint/skills/impl-tracking into .gemini/skills/impl-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "impl-tracking", 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 hashgraph-online/awesome-codex-plugins impl-trackingInstalls 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 hashgraph-online/awesome-codex-plugins --skill impl-tracking -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/JuliusBrussee/blueprint/skills/impl-tracking .github/skills/impl-tracking && 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 "impl-tracking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/JuliusBrussee/blueprint/skills/impl-tracking into .github/skills/impl-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "impl-tracking", 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 hashgraph-online/awesome-codex-plugins --skill impl-tracking -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashgraph-online/awesome-codex-plugins impl-tracking --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/JuliusBrussee/blueprint/skills/impl-tracking .opencode/skills/impl-tracking && 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 "impl-tracking" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/JuliusBrussee/blueprint/skills/impl-tracking into .opencode/skills/impl-tracking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "impl-tracking", 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.
impl-trackingImplementation tracking documents for maintaining living records of what was built, what is pending, what failed, and what dead ends were explored.
Impl Tracking is an agent skill from hashgraph-online/awesome-codex-plugins. Implementation tracking documents for maintaining living records of what was built, what is pending, what failed, and what dead ends were explored. Covers the full tracking document template, dead ends prevention, cross-iteration continuity, spec compaction, and inter-session feedback protocol. Trigger phrases: "implementation tracking", "track progress", "session tracking", "what did the agent do", "dead ends", "failed approaches"
Its SKILL.md is about 4.3k 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 Documents & Office. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 16b4156. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and xml).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Impl Tracking loads about 4.3k tokens when it runs. Until then it costs about 112 tokens; SKILL.md has 1,168 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.
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.
The full file from hashgraph-online/awesome-codex-plugins at commit 16b4156, republished under its Apache-2.0 licence (© hashgraph-online). 1,168 words, ~4,318 tokens.
.claude/skills/impl-tracking/SKILL.md (or your agent's skills folder).Implementation tracking documents are living records that agents read and update every session. They serve as persistent memory across iterations, preventing duplicate work and preserving hard-won knowledge about what works and what does not.
The most valuable information in an implementation tracking document is not what succeeded — it is what failed and why. Dead ends documented today prevent agents from wasting hours retrying the same failed approaches tomorrow.
| Purpose | What It Prevents |
|---|---|
| Cross-iteration continuity | Agents starting from scratch every session |
| Dead end prevention | Agents retrying approaches that already failed |
| Progress visibility | Humans not knowing what was done or what is left |
| Test health awareness | Agents not knowing current test state |
| Issue tracking | Known issues being forgotten between sessions |
| File change tracking | Uncertainty about what files were created or modified |
Without implementation tracking, every agent session begins with expensive rediscovery. With it, agents resume exactly where the last session left off.
Use this template for every implementation tracking document:
# Implementation Tracking: {Domain or Scope}
## Status: {IN_PROGRESS | COMPLETE | BLOCKED}
**Last Updated:** {Date}
**Current Phase:** {Spec | Plan | Implement | Iterate | Monitor}
**Blocking Issues:** {None | Brief description of blockers}
---
## Task Status
| Task ID | Task | Status | Notes |
|---------|------|--------|-------|
| T-1 | {Task description} | DONE | {Completion notes} |
| T-2 | {Task description} | DONE | {Completion notes} |
| T-3 | {Task description} | IN_PROGRESS | {Current state, what remains} |
| T-4 | {Task description} | BLOCKED | {What is blocking, dependency} |
| T-5 | {Task description} | NOT_STARTED | {Prerequisites} |
### Task Dependencies
- T-4 blockedBy T-3 (needs auth module before API integration)
- T-5 blockedBy T-3, T-4
---
## Files Created
| File | Purpose | Spec Reference |
|------|---------|---------------|
| `src/auth/login.{ext}` | Login handler | spec-auth.md R1 |
| `src/auth/session.{ext}` | Session management | spec-auth.md R2 |
| `tests/auth/login.test.{ext}` | Login unit tests | spec-auth.md R1 AC1-3 |
## Files Modified
| File | Change | Reason |
|------|--------|--------|
| `src/app.{ext}` | Added auth middleware | spec-auth.md R3 |
| `src/config.{ext}` | Added session config | spec-auth.md R2 |
---
## Issues & TODOs
- [ ] **Issue:** Session expiry not tested under concurrent access — need load test
- [ ] **TODO:** Add rate limiting to login endpoint (spec-api.md R7)
- [ ] **TODO:** Implement password reset flow (spec-auth.md R4, NOT_STARTED)
- [x] **Resolved:** TypeScript compilation error in session.ts — fixed incorrect import path
---
## Dead Ends & Failed Approaches
### DE-1: JWT with asymmetric keys for session tokens
**What was attempted:** Implemented RS256 JWT tokens with public/private key pair.
**Root cause of failure:** Key rotation complexity exceeded the session management requirements. Added 200+ lines of key management code for no user-visible benefit. Symmetric HS256 with server-side session store is simpler and meets all spec criteria.
**Verdict:** Do not reattempt. Use symmetric tokens with server-side sessions instead.
### DE-2: Redis for session storage
**What was attempted:** Used Redis as the session store backend.
**Root cause of failure:** Redis dependency adds operational complexity. The application's expected concurrent user count (< 10,000) is well within what a database-backed session store handles. Redis would be premature optimization.
**Verdict:** Do not reattempt unless concurrent user requirements change significantly (> 100,000).
### DE-3: Cookie-based CSRF protection
**What was attempted:** Double-submit cookie pattern for CSRF.
**Root cause of failure:** Incompatible with the API's token-based auth flow. Clients send bearer tokens in headers, not cookies. CSRF protection is inherently handled by the token-based approach.
**Verdict:** Do not reattempt. Token-based auth does not need separate CSRF protection.
---
## Test Health
| Test Suite | Passing | Failing | Skipped | Line Coverage |
|------------|---------|---------|---------|---------------|
| Unit tests | 45 | 2 | 0 | 78% |
| Integration | 12 | 1 | 3 | n/a |
| E2E | 0 | 0 | 0 | n/a |
### Failing Tests
- `tests/auth/session.test.{ext}:34` — Session refresh fails when token is expired more than 24h. Needs spec clarification on refresh window.
- `tests/integration/api-auth.test.{ext}:89` — Timeout on concurrent login test. Likely race condition in session creation.
### Test Notes
- E2E tests not yet created (blocked on T-4: API integration)
- Integration test skip: 3 tests require external OAuth provider mock (TODO)
---
## Session Log
### Session 3 (current)
- Completed T-2 (session management)
- Started T-3 (API integration) — 60% complete
- Discovered DE-3 (CSRF not needed with token auth)
- 2 new failing tests identified
### Session 2
- Completed T-1 (login handler)
- Discovered DE-1 (JWT asymmetric keys too complex)
- Discovered DE-2 (Redis premature for this scale)
- Test health: 38 pass, 0 fail
### Session 1
- Set up auth module structure
- Created initial test scaffolding
- Established file ownership: auth/ owned by auth-agentDead ends prevent agents from retrying failed approaches. This is the single most important function of implementation tracking.
Without dead end documentation:
With dead end documentation:
Every dead end entry must include:
### DE-{N}: {Short description of the approach}
**What was attempted:** {Specific description of the approach taken}
**Root cause of failure:** {Why it did not work — a clear technical explanation, not just "it broke"}
**Verdict:** Do not reattempt. {Recommended alternative, or conditions under which the approach might become viable}Implementation tracking documents are the primary mechanism for continuity between iteration loop passes and between human-initiated sessions.
At the start of every iteration or session, the agent:
At the end of every iteration or session, the agent:
┌─────────────────────────────────────┐
│ 1. Read impl tracking │
│ 2. Identify highest-priority task │
│ 3. Check dead ends for this area │
│ 4. Implement │
│ 5. Run validation gates │
│ 6. Update impl tracking │
│ 7. Commit │
└─────────────────────────────────────┘
↓ (next iteration)
┌─────────────────────────────────────┐
│ 1. Read impl tracking (updated) │
│ 2. ... │
└─────────────────────────────────────┘When implementation tracking files exceed approximately 500 lines, they become unwieldy for agents to process. Compaction compresses the file while preserving active context.
impl/archive/impl-{scope}-v{N}.md> **Archive:** Previous tracking history available in impl/archive/impl-all-v2.md
> 12 tasks completed in prior sessions. See archive for details.For structured handoffs between sessions (especially when different humans or automation systems manage sessions), use the inter-session feedback protocol.
<session-report>
<session-id>2026-03-14-session-3</session-id>
<timestamp>2026-03-14T14:30:00Z</timestamp>
<task id="T-1">
<title>Implement session management</title>
<status>DONE</status>
<files-modified>true</files-modified>
<summary>
Implemented session creation, validation, and refresh.
Added server-side session store with database backend.
Created 3 new files, modified 2 existing files.
</summary>
<obstacles kind="NONE"></obstacles>
<next-steps>
Proceed to API integration (T-3). Session module is ready.
</next-steps>
</task>
<task id="T-2">
<title>API endpoint integration</title>
<status>PARTIAL</status>
<files-modified>true</files-modified>
<summary>
Completed GET /users and POST /login endpoints.
PUT /users and DELETE /users not started.
</summary>
<obstacles kind="TEMPORARY">
Waiting for session management to stabilize (now done).
</obstacles>
<next-steps>
Continue with PUT/DELETE endpoints. All dependencies resolved.
</next-steps>
</task>
<task id="T-3">
<title>OAuth provider integration</title>
<status>BLOCKED</status>
<files-modified>false</files-modified>
<summary>
Investigation complete. OAuth provider requires API key registration.
</summary>
<obstacles kind="PERMANENT">
Cannot proceed without OAuth API credentials.
Human action required: register application with OAuth provider.
</obstacles>
<next-steps>
Skip until credentials are available. Focus on other tasks.
</next-steps>
</task>
</session-report>| Field | Values | Purpose |
|---|---|---|
status | DONE, PARTIAL, BLOCKED | Current state of the work item |
files-modified | true, false | Whether code was modified (helps humans prioritize review) |
summary | Free text | What was accomplished — be specific |
obstacles.kind | NONE, TEMPORARY, PERMANENT | TEMPORARY = will resolve on its own; PERMANENT = requires human action |
next-steps | Free text | What the next session should do with this item |
/ck:next-session command consumes this feedback to generate prioritized work itemsFor the full session feedback protocol reference, see
references/session-feedback-protocol.md.
At the end of a session, generate a plan-next-session.md that prioritizes work for the next session:
# Next Session Work Queue
## WI-1: Complete API endpoint integration
- **Category:** feature
- **Size:** M
- **Priority:** high
- **Spec reference:** plan-api.md
- **What to do:** Implement PUT /users and DELETE /users endpoints
- **Files to modify:** src/api/users.{ext}, tests/api/users.test.{ext}
- **Acceptance criteria:**
- [ ] PUT /users/{id} updates user record and returns 200
- [ ] DELETE /users/{id} removes user and returns 204
- [ ] Both endpoints require valid session token
## WI-2: Fix failing session refresh test
- **Category:** bugfix
- **Size:** S
- **Priority:** medium
- **Spec reference:** plan-auth.md
- **What to do:** Investigate and fix session refresh failure for tokens expired > 24h
- **Files to modify:** src/auth/session.{ext}, tests/auth/session.test.{ext}
- **Acceptance criteria:**
- [ ] Session refresh test passes for tokens expired < 24h
- [ ] Clear error message for tokens expired > 24h (if that is the intended behavior)
## WI-3: Create E2E test scaffolding
- **Category:** test
- **Size:** M
- **Priority:** medium
- **Spec reference:** plan-testing.md
- **What to do:** Set up E2E test framework and create smoke tests
- **Files to modify:** tests/e2e/setup.{ext}, tests/e2e/smoke.test.{ext}
- **Acceptance criteria:**
- [ ] E2E framework runs successfully
- [ ] Smoke test verifies application starts and login worksThis removes the orientation cost at the start of each session — agents begin productive work immediately. The next agent reads this file and begins working immediately on the highest-priority item.
ck:cavekit-writingImplementation tracking references specs by requirement ID. When a task is completed, its acceptance criteria map back to spec requirements. When dead ends are found, they may reveal spec gaps that need revision.
ck:validation-firstTest health in the tracking document reflects validation gate results. Failing tests indicate which gates are not passing. The tracking document records which gates each task must clear.
ck:context-architectureImplementation tracking documents live in context/impl/. When files grow too large, archive to context/impl/archive/. The CLAUDE.md in context/impl/ instructs agents on tracking conventions.
ck:methodologyImplementation tracking is used primarily during the Implement and Iterate phases of the Hunt. The iteration loop reads and updates tracking documents every pass. The Monitor phase reviews tracking documents for progress signals.
© hashgraph-online, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in plugins/JuliusBrussee/blueprint/skills/impl-tracking of hashgraph-online/awesome-codex-plugins.
Open the folder on GitHubat commit 16b4156
Impl Tracking 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 |
|---|---|---|---|---|---|---|
| Impl Tracking this skillhashgraph-online/awesome-codex-plugins | 1.2k | — | ~4.3k | Automated safety check: Pass | Apache-2.0 | |
| Markdown Article FormatterJimLiu/baoyu-skills | 26k | 6 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Gzh Designisjiamu/gzh-design-skill | 3.9k | 1 repos | ~2.2k | Automated safety check: Pass | AGPL-3.0 |
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
isjiamu/gzh-design-skill
微信公众号文章排版引擎,将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取,自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入(非 Markdown…
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
Categories
Implementation tracking documents for maintaining living records of what was built, what is pending, what failed, and what dead ends were explored. Impl Tracking is an agent skill from hashgraph-online/awesome-codex-plugins. Implementation tracking documents for maintaining living records of what was built, what is pending, what failed, and what dead ends were explored.
Impl Tracking fits situations like: phrases: implementation tracking; session tracking; what did the agent do; failed approaches.
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill impl-tracking -a claude-code`. Or copy the skill folder (plugins/JuliusBrussee/blueprint/skills/impl-tracking in hashgraph-online/awesome-codex-plugins) into .claude/skills/impl-tracking in your project. Claude Code loads it when a task matches its description.
Run `npx skills add hashgraph-online/awesome-codex-plugins --skill impl-tracking -a codex`. Or copy the skill folder (plugins/JuliusBrussee/blueprint/skills/impl-tracking in hashgraph-online/awesome-codex-plugins) into .agents/skills/impl-tracking in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill impl-tracking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/impl-tracking, .gemini/skills/impl-tracking, .github/skills/impl-tracking and .opencode/skills/impl-tracking in your project.
SKILL.md names no scripts, command-line tools or credentials: Impl Tracking is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
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.
Impl Tracking is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Impl Tracking: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,232 GitHub stars. The repository holds 736 skills in this directory. The repository was last updated on October 6, 2026.
Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.