[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78499QGC8RGTDWV8VSZN0HT":3,"skill-same:01M78499QGC8RGTDWV8VSZN0HT":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M78499QGC8RGTDWV8VSZN0HT","tc-tracker",null,"Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init\u002Fcreate\u002Fupdate\u002Fstatus\u002Fresume\u002Fclose\u002Fexport workflows for structured code change documentation.","motivatedc-creator\u002FSaafy","motivatedc-creator","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F250662783?v=4","01M782H2D8C7XJGXMJC3YHQAWK","Happy Haris","01M782H2ERMBYEM1NSPPPC06S0",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"tc-tracker\"\ndescription: \"Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init\u002Fcreate\u002Fupdate\u002Fstatus\u002Fresume\u002Fclose\u002Fexport workflows for structured code change documentation.\"\n---\n\n# TC Tracker\n\nTrack every code change with structured JSON records, an enforced state machine, and a session handoff format that lets a new AI session resume work cleanly when a previous one expires.\n\n## Overview\n\nA Technical Change (TC) is a structured record that captures **what** changed, **why** it changed, **who** changed it, **when** it changed, **how it was tested**, and **where work stands** for the next session. Records live as JSON in `docs\u002FTC\u002F` inside the target project, validated against a strict schema and a state machine.\n\n**Use this skill when the user:**\n- Asks to \"track this change\" or wants an audit trail for code modifications\n- Wants to hand off in-progress work to a future AI session\n- Needs structured release notes that go beyond commit messages\n- Onboards an existing project and wants retroactive change documentation\n- Asks for `\u002Ftc init`, `\u002Ftc create`, `\u002Ftc update`, `\u002Ftc status`, `\u002Ftc resume`, or `\u002Ftc close`\n\n**Do NOT use this skill when:**\n- The user only wants a changelog from git history (use `engineering\u002Fchangelog-generator`)\n- The user only wants to track tech debt items (use `engineering\u002Ftech-debt-tracker`)\n- The change is trivial (typo, formatting) and won't affect behavior\n\n## Storage Layout\n\nEach project stores TCs at `{project_root}\u002Fdocs\u002FTC\u002F`:\n\n```\ndocs\u002FTC\u002F\n├── tc_config.json          # Project settings\n├── tc_registry.json        # Master index + statistics\n├── records\u002F\n│   └── TC-001-04-05-26-user-auth\u002F\n│       └── tc_record.json  # Source of truth\n└── evidence\u002F\n    └── TC-001\u002F             # Log snippets, command output, screenshots\n```\n\n## TC ID Convention\n\n- **Parent TC:** `TC-NNN-MM-DD-YY-functionality-slug` (e.g., `TC-001-04-05-26-user-authentication`)\n- **Sub-TC:** `TC-NNN.A` or `TC-NNN.A.1` (letter = revision, digit = sub-revision)\n- `NNN` is sequential, `MM-DD-YY` is the creation date, slug is kebab-case.\n\n## State Machine\n\n```\nplanned -> in_progress -> implemented -> tested -> deployed\n   |            |              |           |          |\n   +-> blocked -+              +- in_progress \u003C-------+\n        |                          (rework \u002F hotfix)\n        +-> planned\n```\n\n> See [references\u002Flifecycle.md](references\u002Flifecycle.md) for the full transition table and recovery flows.\n\n## Workflow Commands\n\nThe skill ships five Python scripts that perform deterministic, stdlib-only operations on TC records. Each one supports `--help` and `--json`.\n\n### 1. Initialize tracking in a project\n\n```bash\npython3 scripts\u002Ftc_init.py --project \"My Project\" --root .\n```\n\nCreates `docs\u002FTC\u002F`, `docs\u002FTC\u002Frecords\u002F`, `docs\u002FTC\u002Fevidence\u002F`, `tc_config.json`, and `tc_registry.json`. Idempotent — re-running reports \"already initialized\" with current stats.\n\n### 2. Create a new TC record\n\n```bash\npython3 scripts\u002Ftc_create.py \\\n  --root . \\\n  --name \"user-authentication\" \\\n  --title \"Add JWT-based user authentication\" \\\n  --scope feature \\\n  --priority high \\\n  --summary \"Adds JWT login + middleware\" \\\n  --motivation \"Required for protected endpoints\"\n```\n\nGenerates the next sequential TC ID, creates the record directory, writes a fully populated `tc_record.json` (status `planned`, R1 creation revision), and updates the registry.\n\n### 3. Update a TC record\n\n```bash\n# Status transition (validated against the state machine)\npython3 scripts\u002Ftc_update.py --root . --tc-id TC-001-04-05-26-user-auth \\\n  --set-status in_progress --reason \"Starting implementation\"\n\n# Add a file\npython3 scripts\u002Ftc_update.py --root . --tc-id TC-001-04-05-26-user-auth \\\n  --add-file src\u002Fauth.py:created\n\n# Append handoff data\npython3 scripts\u002Ftc_update.py --root . --tc-id TC-001-04-05-26-user-auth \\\n  --handoff-progress \"JWT middleware wired up\" \\\n  --handoff-next \"Write integration tests\" \\\n  --handoff-next \"Update README\"\n```\n\nEvery change appends a sequential `R\u003Cn>` revision entry, refreshes `updated`, and re-validates against the schema before writing atomically (`.tmp` then rename).\n\n### 4. View status\n\n```bash\n# Single TC\npython3 scripts\u002Ftc_status.py --root . --tc-id TC-001-04-05-26-user-auth\n\n# All TCs (registry summary)\npython3 scripts\u002Ftc_status.py --root . --all --json\n```\n\n### 5. Validate a record or registry\n\n```bash\npython3 scripts\u002Ftc_validator.py --record docs\u002FTC\u002Frecords\u002FTC-001-...\u002Ftc_record.json\npython3 scripts\u002Ftc_validator.py --registry docs\u002FTC\u002Ftc_registry.json\n```\n\nValidator enforces the schema, checks state-machine legality, verifies sequential `R\u003Cn>` and `T\u003Cn>` IDs, and asserts approval consistency (`approved=true` requires `approved_by` and `approved_date`).\n\n> See [references\u002Ftc-schema.md](references\u002Ftc-schema.md) for the full schema.\n\n## Slash-Command Dispatcher\n\nThe repo ships a `\u002Ftc` slash command at `commands\u002Ftc.md` that dispatches to these scripts based on subcommand:\n\n| Command | Action |\n|---------|--------|\n| `\u002Ftc init` | Run `tc_init.py` for the current project |\n| `\u002Ftc create \u003Cname>` | Prompt for fields, run `tc_create.py` |\n| `\u002Ftc update \u003Ctc-id>` | Apply user-described changes via `tc_update.py` |\n| `\u002Ftc status [tc-id]` | Run `tc_status.py` |\n| `\u002Ftc resume \u003Ctc-id>` | Display handoff, archive prior session, start a new one |\n| `\u002Ftc close \u003Ctc-id>` | Transition to `deployed`, set approval |\n| `\u002Ftc export` | Re-render all derived artifacts |\n| `\u002Ftc dashboard` | Re-render the registry summary |\n\nThe slash command is the user interface; the Python scripts are the engine.\n\n## Session Handoff Format\n\nThe handoff block lives at `session_context.handoff` inside each TC and is the single most important field for AI continuity. It contains:\n\n- `progress_summary` — what has been done\n- `next_steps` — ordered list of remaining actions\n- `blockers` — anything preventing progress\n- `key_context` — critical decisions, gotchas, patterns the next bot must know\n- `files_in_progress` — files being edited and their state (`editing`, `needs_review`, `partially_done`, `ready`)\n- `decisions_made` — architectural decisions with rationale and timestamp\n\n> See [references\u002Fhandoff-format.md](references\u002Fhandoff-format.md) for the full structure and fill-out rules.\n\n## Validation Rules (Always Enforced)\n\n1. **State machine** — only valid transitions are allowed.\n2. **Sequential IDs** — `revision_history` uses `R1, R2, R3...`; `test_cases` uses `T1, T2, T3...`.\n3. **Append-only history** — revision entries are never modified or deleted.\n4. **Approval consistency** — `approved=true` requires `approved_by` and `approved_date`.\n5. **TC ID format** — must match `TC-NNN-MM-DD-YY-slug`.\n6. **Sub-TC ID format** — must match `TC-NNN.A` or `TC-NNN.A.N`.\n7. **Atomic writes** — JSON is written to `.tmp` then renamed.\n8. **Registry stats** — recomputed on every registry write.\n\n## Non-Blocking Bookkeeping Pattern\n\nTC tracking must NOT interrupt the main workflow.\n\n- **Never stop to update TC records inline.** Keep coding.\n- At natural milestones, spawn a background subagent to update the record.\n- Surface questions only when genuinely needed (\"This work doesn't match any active TC — create one?\"), and ask once per session, not per file.\n- At session end, write a final handoff block before closing.\n\n## Retroactive Bulk Creation\n\nFor onboarding an existing project with undocumented history, build a `retro_changelog.json` (one entry per logical change) and feed it to `tc_create.py` in a loop, or extend the script for batch mode. Group commits by feature, not by file.\n\n## Anti-Patterns\n\n| Anti-pattern | Why it's bad | Do this instead |\n|--------------|--------------|-----------------|\n| Editing `revision_history` to \"fix\" a typo | History is append-only — tampering destroys the audit trail | Add a new revision that corrects the field |\n| Skipping the state machine (\"just set status to deployed\") | Bypasses validation and hides skipped phases | Walk through `in_progress -> implemented -> tested -> deployed` |\n| Creating one TC per file changed | Fragments related work and explodes the registry | One TC per logical unit (feature, fix, refactor) |\n| Updating TC inline between every code edit | Slows the main agent, wastes context | Spawn a background subagent at milestones |\n| Marking `approved=true` without `approved_by` | Validator will reject; misleading audit trail | Always set `approved_by` and `approved_date` together |\n| Overwriting `tc_record.json` directly with a text editor | Risks corruption mid-write and skips validation | Use `tc_update.py` (atomic write + schema check) |\n| Putting secrets in `notes` or evidence | Records are committed to the repo | Reference an env var or external secret store |\n| Reusing TC IDs after deletion | Breaks the sequential guarantee and confuses history | Increment forward only — never recycle |\n| Letting `next_steps` go stale | Defeats the purpose of handoff | Update on every milestone, even if it's \"nothing changed\" |\n\n## Cross-References\n\n- `engineering\u002Fchangelog-generator` — Generates Keep-a-Changelog release notes from Conventional Commits. Pair it with TC tracker: TC for the granular per-change audit trail, changelog for user-facing release notes.\n- `engineering\u002Ftech-debt-tracker` — For tracking long-lived debt items rather than discrete code changes.\n- `engineering\u002Ffocused-fix` — When a bug fix needs systematic feature-wide repair, run `\u002Ffocused-fix` first then capture the result as a TC.\n- `project-management\u002Fdecision-log` — Architectural decisions made inside a TC's `decisions_made` block can also be promoted to a project-wide decision log.\n- `engineering-team\u002Fcode-reviewer` — Pre-merge review fits naturally into the `tested -> deployed` transition; capture the reviewer in `approval.approved_by`.\n\n## References in This Skill\n\n- [references\u002Ftc-schema.md](references\u002Ftc-schema.md) — Full JSON schema for TC records and the registry.\n- [references\u002Flifecycle.md](references\u002Flifecycle.md) — State machine, valid transitions, and recovery flows.\n- [references\u002Fhandoff-format.md](references\u002Fhandoff-format.md) — Session handoff structure and best practices.\n","# TC Tracker\n\nTrack every code change with structured JSON records, an enforced state machine, and a session handoff format that lets a new AI session resume work cleanly when a previous one expires.\n\n## Overview\n\nA Technical Change (TC) is a structured record that captures **what** changed, **why** it changed, **who** changed it, **when** it changed, **how it was tested**, and **where work stands** for the next session. Records live as JSON in `docs\u002FTC\u002F` inside the target project, validated against a strict schema and a state machine.\n\n**Use this skill when the user:**\n- Asks to \"track this change\" or wants an audit trail for code modifications\n- Wants to hand off in-progress work to a future AI session\n- Needs structured release notes that go beyond commit messages\n- Onboards an existing project and wants retroactive change documentation\n- Asks for `\u002Ftc init`, `\u002Ftc create`, `\u002Ftc update`, `\u002Ftc status`, `\u002Ftc resume`, or `\u002Ftc close`\n\n**Do NOT use this skill when:**\n- The user only wants a changelog from git history (use `engineering\u002Fchangelog-generator`)\n- The user only wants to track tech debt items (use `engineering\u002Ftech-debt-tracker`)\n- The change is trivial (typo, formatting) and won't affect behavior\n\n## Storage Layout\n\nEach project stores TCs at `{project_root}\u002Fdocs\u002FTC\u002F`:\n\n```\ndocs\u002FTC\u002F\n├── tc_config.json          # Project settings\n├── tc_registry.json        # Master index + statistics\n├── records\u002F\n│   └── TC-001-04-05-26-user-auth\u002F\n│       └── tc_record.json  # Source of truth\n└── evidence\u002F\n    └── TC-001\u002F             # Log snippets, command output, screenshots\n```\n\n## TC ID Convention\n\n- **Parent TC:** `TC-NNN-MM-DD-YY-functionality-slug` (e.g., `TC-001-04-05-26-user-authentication`)\n- **Sub-TC:** `TC-NNN.A` or `TC-NNN.A.1` (letter = revision, digit = sub-revision)\n- `NNN` is sequential, `MM-DD-YY` is the creation date, slug is kebab-case.\n\n## State Machine\n\n```\nplanned -> in_progress -> implemented -> tested -> deployed\n   |            |              |           |          |\n   +-> blocked -+              +- in_progress \u003C-------+\n        |                          (rework \u002F hotfix)\n        +-> planned\n```\n\n> See [references\u002Flifecycle.md](references\u002Flifecycle.md) for the full transition table and recovery flows.\n\n## Workflow Commands\n\nThe skill ships five Python scripts that perform deterministic, stdlib-only operations on TC records. Each one supports `--help` and `--json`.\n\n### 1. Initialize tracking in a project\n\n```bash\npython3 scripts\u002Ftc_init.py --project \"My Project\" --root .\n```\n\nCreates `docs\u002FTC\u002F`, `docs\u002FTC\u002Frecords\u002F`, `docs\u002FTC\u002Fevidence\u002F`, `tc_config.json`, and `tc_registry.json`. Idempotent — re-running reports \"already initialized\" with current stats.\n\n### 2. Create a new TC record\n\n```bash\npython3 scripts\u002Ftc_create.py \\\n  --root . \\\n  --name \"user-authentication\" \\\n  --title \"Add JWT-based user authentication\" \\\n  --scope feature \\\n  --priority high \\\n  --summary \"Adds JWT login + middleware\" \\\n  --motivation \"Required for protected endpoints\"\n```\n\nGenerates the next sequential TC ID, creates the record directory, writes a fully populated `tc_record.json` (status `planned`, R1 creation revision), and updates the registry.\n\n### 3. Update a TC record\n\n```bash\n# Status transition (validated against the state machine)\npython3 scripts\u002Ftc_update.py --root . --tc-id TC-001-04-05-26-user-auth \\\n  --set-status in_progress --reason \"Starting implementation\"\n\n# Add a file\npython3 scripts\u002Ftc_update.py --root . --tc-id TC-001-04-05-26-user-auth \\\n  --add-file src\u002Fauth.py:created\n\n# Append handoff data\npython3 scripts\u002Ftc_update.py --root . --tc-id TC-001-04-05-26-user-auth \\\n  --handoff-progress \"JWT middleware wired up\" \\\n  --handoff-next \"Write integration tests\" \\\n  --handoff-next \"Update README\"\n```\n\nEvery change appends a sequential `R\u003Cn>` revision entry, refreshes `updated`, and re-validates against the schema before writing atomically (`.tmp` then rename).\n\n### 4. View status\n\n```bash\n# Single TC\npython3 scripts\u002Ftc_status.py --root . --tc-id TC-001-04-05-26-user-auth\n\n# All TCs (registry summary)\npython3 scripts\u002Ftc_status.py --root . --all --json\n```\n\n### 5. Validate a record or registry\n\n```bash\npython3 scripts\u002Ftc_validator.py --record docs\u002FTC\u002Frecords\u002FTC-001-...\u002Ftc_record.json\npython3 scripts\u002Ftc_validator.py --registry docs\u002FTC\u002Ftc_registry.json\n```\n\nValidator enforces the schema, checks state-machine legality, verifies sequential `R\u003Cn>` and `T\u003Cn>` IDs, and asserts approval consistency (`approved=true` requires `approved_by` and `approved_date`).\n\n> See [references\u002Ftc-schema.md](references\u002Ftc-schema.md) for the full schema.\n\n## Slash-Command Dispatcher\n\nThe repo ships a `\u002Ftc` slash command at `commands\u002Ftc.md` that dispatches to these scripts based on subcommand:\n\n| Command | Action |\n|---------|--------|\n| `\u002Ftc init` | Run `tc_init.py` for the current project |\n| `\u002Ftc create \u003Cname>` | Prompt for fields, run `tc_create.py` |\n| `\u002Ftc update \u003Ctc-id>` | Apply user-described changes via `tc_update.py` |\n| `\u002Ftc status [tc-id]` | Run `tc_status.py` |\n| `\u002Ftc resume \u003Ctc-id>` | Display handoff, archive prior session, start a new one |\n| `\u002Ftc close \u003Ctc-id>` | Transition to `deployed`, set approval |\n| `\u002Ftc export` | Re-render all derived artifacts |\n| `\u002Ftc dashboard` | Re-render the registry summary |\n\nThe slash command is the user interface; the Python scripts are the engine.\n\n## Session Handoff Format\n\nThe handoff block lives at `session_context.handoff` inside each TC and is the single most important field for AI continuity. It contains:\n\n- `progress_summary` — what has been done\n- `next_steps` — ordered list of remaining actions\n- `blockers` — anything preventing progress\n- `key_context` — critical decisions, gotchas, patterns the next bot must know\n- `files_in_progress` — files being edited and their state (`editing`, `needs_review`, `partially_done`, `ready`)\n- `decisions_made` — architectural decisions with rationale and timestamp\n\n> See [references\u002Fhandoff-format.md](references\u002Fhandoff-format.md) for the full structure and fill-out rules.\n\n## Validation Rules (Always Enforced)\n\n1. **State machine** — only valid transitions are allowed.\n2. **Sequential IDs** — `revision_history` uses `R1, R2, R3...`; `test_cases` uses `T1, T2, T3...`.\n3. **Append-only history** — revision entries are never modified or deleted.\n4. **Approval consistency** — `approved=true` requires `approved_by` and `approved_date`.\n5. **TC ID format** — must match `TC-NNN-MM-DD-YY-slug`.\n6. **Sub-TC ID format** — must match `TC-NNN.A` or `TC-NNN.A.N`.\n7. **Atomic writes** — JSON is written to `.tmp` then renamed.\n8. **Registry stats** — recomputed on every registry write.\n\n## Non-Blocking Bookkeeping Pattern\n\nTC tracking must NOT interrupt the main workflow.\n\n- **Never stop to update TC records inline.** Keep coding.\n- At natural milestones, spawn a background subagent to update the record.\n- Surface questions only when genuinely needed (\"This work doesn't match any active TC — create one?\"), and ask once per session, not per file.\n- At session end, write a final handoff block before closing.\n\n## Retroactive Bulk Creation\n\nFor onboarding an existing project with undocumented history, build a `retro_changelog.json` (one entry per logical change) and feed it to `tc_create.py` in a loop, or extend the script for batch mode. Group commits by feature, not by file.\n\n## Anti-Patterns\n\n| Anti-pattern | Why it's bad | Do this instead |\n|--------------|--------------|-----------------|\n| Editing `revision_history` to \"fix\" a typo | History is append-only — tampering destroys the audit trail | Add a new revision that corrects the field |\n| Skipping the state machine (\"just set status to deployed\") | Bypasses validation and hides skipped phases | Walk through `in_progress -> implemented -> tested -> deployed` |\n| Creating one TC per file changed | Fragments related work and explodes the registry | One TC per logical unit (feature, fix, refactor) |\n| Updating TC inline between every code edit | Slows the main agent, wastes context | Spawn a background subagent at milestones |\n| Marking `approved=true` without `approved_by` | Validator will reject; misleading audit trail | Always set `approved_by` and `approved_date` together |\n| Overwriting `tc_record.json` directly with a text editor | Risks corruption mid-write and skips validation | Use `tc_update.py` (atomic write + schema check) |\n| Putting secrets in `notes` or evidence | Records are committed to the repo | Reference an env var or external secret store |\n| Reusing TC IDs after deletion | Breaks the sequential guarantee and confuses history | Increment forward only — never recycle |\n| Letting `next_steps` go stale | Defeats the purpose of handoff | Update on every milestone, even if it's \"nothing changed\" |\n\n## Cross-References\n\n- `engineering\u002Fchangelog-generator` — Generates Keep-a-Changelog release notes from Conventional Commits. Pair it with TC tracker: TC for the granular per-change audit trail, changelog for user-facing release notes.\n- `engineering\u002Ftech-debt-tracker` — For tracking long-lived debt items rather than discrete code changes.\n- `engineering\u002Ffocused-fix` — When a bug fix needs systematic feature-wide repair, run `\u002Ffocused-fix` first then capture the result as a TC.\n- `project-management\u002Fdecision-log` — Architectural decisions made inside a TC's `decisions_made` block can also be promoted to a project-wide decision log.\n- `engineering-team\u002Fcode-reviewer` — Pre-merge review fits naturally into the `tested -> deployed` transition; capture the reviewer in `approval.approved_by`.\n\n## References in This Skill\n\n- [references\u002Ftc-schema.md](references\u002Ftc-schema.md) — Full JSON schema for TC records and the registry.\n- [references\u002Flifecycle.md](references\u002Flifecycle.md) — State machine, valid transitions, and recovery flows.\n- [references\u002Fhandoff-format.md](references\u002Fhandoff-format.md) — Session handoff structure and best practices.\n",{"name":5,"description":7},"main","55ae24ca5523c0499dd70b2874ef674a0e66a85b","engineering\u002Fskills\u002Ftc-tracker","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator","2026-07-04 02:45:55",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add motivatedc-creator\u002FSaafy --skill tc-tracker",{"tool":36,"command":37},"bunx","bunx skills add motivatedc-creator\u002FSaafy --skill tc-tracker",{"tool":39,"command":40},"pnpm","pnpm dlx skills add motivatedc-creator\u002FSaafy --skill tc-tracker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002FSKILL.md",true,[44,50,54,58,62,68,72,76,80],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"README.md","REFERENCE","参考文档",2278,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002FREADME.md",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fhandoff-format.md",5291,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002Freferences\u002Fhandoff-format.md",{"path":55,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Flifecycle.md",4037,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002Freferences\u002Flifecycle.md",{"path":59,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ftc-schema.md",5386,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002Freferences\u002Ftc-schema.md",{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"scripts\u002Ftc_create.py","SCRIPT","脚本",9936,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002Fscripts\u002Ftc_create.py",{"path":69,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":70,"sourceHtmlUrl":71},"scripts\u002Ftc_init.py",6861,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002Fscripts\u002Ftc_init.py",{"path":73,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":74,"sourceHtmlUrl":75},"scripts\u002Ftc_status.py",7335,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002Fscripts\u002Ftc_status.py",{"path":77,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Ftc_update.py",14181,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002Fscripts\u002Ftc_update.py",{"path":81,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Ftc_validator.py",14226,"https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Ftc-tracker\u002Fscripts\u002Ftc_validator.py",[85,92,99,106,113,120],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M78558T3RQ22S1B5H0FJAY1Y","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7854YEAAV883M2PKS04TQEK","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7854NCGDBQ6Q0QG2YY4VHSX","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M78549YZMPYGC1F6S7ZJ4VF8","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M78541PWEQMBPN91PEZZK8H7","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7853P7CWJNW5G0Z99YB6H5D","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fmotivatedc-creator\u002FSaafy\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]