[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PZP4S22J5RTKHMXW84D01F":3,"skill-same:01M6PZP4S22J5RTKHMXW84D01F":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":32,"commitSha":61,"skillDirectory":62,"forksCount":13,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":65,"install":66,"resources":79},"01M6PZP4S22J5RTKHMXW84D01F","tree-ring-memory",null,"Use Tree Ring Memory for local-first AI-agent memory lifecycle work: recall, evidence, audit, forgetting, and consolidation without transcript dumping.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Ftree-ring-memory\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"memory","tree","tree ring memory","agent-memory","for","consolidation","critical","local","ai-agent","main","community","cli","opencode","evidence","work","sqlite","audit","transcript","development","gemini","2026-11-10 10:12:30",false,"---\nname: tree-ring-memory\ndescription: \"Use Tree Ring Memory for local-first AI-agent memory lifecycle work: recall, evidence, audit, forgetting, and consolidation without transcript dumping.\"\ncategory: development\nrisk: critical\nsource: community\nsource_repo: TerminallyLazy\u002FTree-Ring-Memory\nsource_type: community\ndate_added: \"2026-07-08\"\nauthor: TerminallyLazy\ntags: [agent-memory, local-first, recall, privacy, codex, sqlite, cli]\ntools: [claude, codex, cursor, gemini, antigravity, opencode]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002FTree-Ring-Memory\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# Tree Ring Memory\n\n## Overview\n\nTree Ring Memory is a framework-agnostic, local-first memory lifecycle layer for\nAI agents. Use this skill when an agent should recall, preserve, audit, or\nforget durable project memory without treating raw conversation transcripts as\nmemory.\n\nThe public runtime is a Rust CLI\u002FTUI with local SQLite\u002FFTS storage, scoped\nrecall, evidence records, audit, deterministic consolidation, maintenance,\nDOX\u002FRevolve source adapters, framework discovery, redaction, and explicit\nforgetting.\n\n## When to Use This Skill\n\n- Use before resuming a project where prior decisions, warnings, preferences,\n  or failed approaches may matter.\n- Use before changing architecture, storage, security, privacy, release, or\n  agent-memory behavior.\n- Use when the user asks to remember, recall, audit, redact, forget, or\n  consolidate agent memory.\n- Use after tests, reviews, incidents, or production behavior validate a lesson\n  future agents should preserve.\n- Use when a project contains `.tree-ring\u002FSKILL.md`, `.tree-ring\u002FCLI.md`, or\n  other Tree Ring bridge files.\n\n## How It Works\n\n### Step 1: Discover Local Guidance\n\nCheck whether the current project already has Tree Ring guidance:\n\n```bash\ntest -f .tree-ring\u002FSKILL.md && sed -n '1,220p' .tree-ring\u002FSKILL.md\ntest -f .tree-ring\u002FCLI.md && sed -n '1,220p' .tree-ring\u002FCLI.md\n```\n\nTreat project-local `.tree-ring` files as more authoritative than generic\nexamples in this skill. If the CLI is installed, inspect the current command\nsurface before assuming flags:\n\n```bash\ntree-ring --help\ntree-ring recall --help\ntree-ring remember --help\ntree-ring evidence --help\ntree-ring audit --help\ntree-ring forget --help\n```\n\nIf Tree Ring is not installed, resolve the actual project root and explain the\nexact project-local download before obtaining explicit approval to fetch it.\nDownload the official, version-pinned `v0.15.0\u002Finstall.sh` to a temporary file,\nverify its SHA-256 is\n`ef0d5eb8f09cbe2e4c3abe80ee9a98a56759c89ad4ddd103d6c68314cd653ade`,\ninspect it, then run it. The pinned source is\n`https:\u002F\u002Fraw.githubusercontent.com\u002FTerminallyLazy\u002FTree-Ring-Memory\u002Fv0.15.0\u002Finstall.sh`.\n\n```bash\ncd \u003Cproject-root>\nsh \u003Cverified-installer-path> --project --init --release v0.15.0 --no-animation\n```\n\nDo not pipe a network response directly to a shell. After verification and\ninspection, show the exact installer command and obtain explicit approval again\nbefore executing it. For an installed global CLI, initialize from the project root with\n`tree-ring --root .tree-ring init`; for a project-local CLI, use\n`.tree-ring\u002Fbin\u002Ftree-ring --root .tree-ring init`.\n\nCheck for a newer release without changing files using\n`tree-ring update --check`. Run `tree-ring update` only with user authorization,\nthen rerun `init` in each project root to refresh managed guidance while\npreserving custom content.\n\n## Step 2: Recall Before Risky Work\n\nUse narrow, project-scoped recall first:\n\n```bash\ntree-ring recall \"release behavior\" --project example-service\ntree-ring recall \"sqlite migration\" --project example-service\ntree-ring recall \"user preference\"\n```\n\nUse recalled memory as context, not authority. Verify it against current source\nfiles, tests, docs, issues, pull requests, logs, and runtime state before making\nchanges.\n\n## Step 3: Write Only Durable Memory\n\nWrite concise memory only when it is likely to help future agents:\n\n```bash\ntree-ring remember \"Run project-scoped recall before release changes.\" --event-type lesson --scope project\n```\n\nPrefer specific event types when supported locally:\n\n- `decision`\n- `lesson`\n- `warning`\n- `correction`\n- `user_preference`\n- `tool_result`\n- `summary`\n- `hypothesis`\n\nStore the durable lesson, decision, warning, or follow-up. Do not store the\nfull conversation.\n\n## Step 4: Record Evidence for Evaluated Outcomes\n\nUse evidence records for test runs, incidents, reviewed changes, or other\nevaluated outcomes:\n\n```bash\ntree-ring evidence \\\n  \"Installer smoke test passed in an isolated HOME.\" \\\n  --outcome observed \\\n  --evidence-ref \"ci\u002Finstall-smoke\u002F2026-07-08\"\n```\n\nOutcome guidance:\n\n- `promoted`: durable truth backed by strong evidence\n- `rejected`: failed or rolled-back approach worth keeping visible\n- `deferred`: unresolved idea or future option\n- `observed`: normal evaluated result\n\nDo not promote weak, stale, or unreviewed claims to durable truth.\n\n## Step 5: Use Source Adapters Carefully\n\nWhen a repo has structured source records, run dry runs first:\n\n```bash\ntree-ring dox sync --source-root . --dry-run\ntree-ring revolve sync --source-root revolve --dry-run\ntree-ring integrations scan --source-root .\n```\n\nOnly write adapter summaries when they are concise, source-linked, useful, and\nprivacy-safe. Imported memory does not replace the underlying `AGENTS.md`,\nRevolve record, test, pull request, issue, or documentation.\n\n## Ring Selection\n\nUse the smallest durable ring that fits:\n\n- `cambium`: active or recent task context\n- `outer`: recent decisions and task lessons\n- `inner`: older compressed project knowledge\n- `heartwood`: durable high-confidence truths\n- `scar`: failures, regressions, rejected approaches, warnings\n- `seed`: unresolved ideas, hypotheses, follow-ups\n\nPrefer `outer` or `seed` unless the user confirms durability or the evidence is\nstrong.\n\n## Best Practices\n\n- Recall before risky or repeat work.\n- Keep project memory project-scoped unless it is a durable cross-project user\n  preference.\n- Attach source references such as file paths, issue ids, PR ids, evaluation\n  runs, or docs paths.\n- Re-check current source files and runtime state before acting on recalled\n  memory.\n- Ask at closeout what future agents should remember, avoid, or revisit.\n- Use redaction, deletion, or supersession when memory is wrong, stale,\n  sensitive, or replaced by a newer decision.\n\n## Security & Safety Notes\n\n- Never use Tree Ring Memory as a hidden recorder.\n- Do not store secrets, credentials, tokens, private keys, recovery codes, raw\n  chain-of-thought, or temporary scratchpad content.\n- Do not store sensitive personal data unless the user explicitly asks and the\n  retention boundary is safe.\n- Do not store copyrighted source text beyond short allowed excerpts.\n- Do not run installer, network, destructive, or mutation commands without\n  explicit user approval and a clear target environment.\n- Treat all examples as commands to adapt after checking local `--help`, not as\n  guaranteed command surfaces.\n\n## Limitations\n\n- Tree Ring Memory is not a replacement for source control, issue trackers,\n  documentation, tests, logs, or live runtime verification.\n- Recalled memory can be stale or wrong. Always verify important claims against\n  the current project before using them to make changes.\n- The CLI surface can change across releases. Prefer local `.tree-ring`\n  guidance and `tree-ring --help` over copied command examples.\n- It should not be used for secret storage, comprehensive transcript archives,\n  compliance retention, or unreviewed collection of sensitive personal data.\n- Cross-agent interoperability depends on each tool's ability to call the local\n  CLI or read project-local guidance files.\n\n## Common Pitfalls\n\n- **Problem:** Recalled memory conflicts with current source.\n  **Solution:** Treat source files, tests, docs, and runtime evidence as\n  authoritative; supersede or forget stale memory.\n\n- **Problem:** Memory starts becoming transcript storage.\n  **Solution:** Store only durable decisions, warnings, preferences, outcomes,\n  and follow-ups.\n\n- **Problem:** A lesson is useful but contains sensitive detail.\n  **Solution:** Store a redacted summary or do not store it.\n\n## Related Skills\n\n- `@agent-memory-systems` - Use for broad agent-memory architecture choices.\n- `@agent-memory` - Use for the listed hybrid memory MCP system.\n- `@planning-with-files` - Use when simple persistent files are enough.\n\n## Additional Resources\n\n- Tree Ring Memory repository: \u003Chttps:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002FTree-Ring-Memory>\n- Codex plugin wrapper: \u003Chttps:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002Ftree-ring-memory-codex-plugin>\n","# Tree Ring Memory\n\n## Overview\n\nTree Ring Memory is a framework-agnostic, local-first memory lifecycle layer for\nAI agents. Use this skill when an agent should recall, preserve, audit, or\nforget durable project memory without treating raw conversation transcripts as\nmemory.\n\nThe public runtime is a Rust CLI\u002FTUI with local SQLite\u002FFTS storage, scoped\nrecall, evidence records, audit, deterministic consolidation, maintenance,\nDOX\u002FRevolve source adapters, framework discovery, redaction, and explicit\nforgetting.\n\n## When to Use This Skill\n\n- Use before resuming a project where prior decisions, warnings, preferences,\n  or failed approaches may matter.\n- Use before changing architecture, storage, security, privacy, release, or\n  agent-memory behavior.\n- Use when the user asks to remember, recall, audit, redact, forget, or\n  consolidate agent memory.\n- Use after tests, reviews, incidents, or production behavior validate a lesson\n  future agents should preserve.\n- Use when a project contains `.tree-ring\u002FSKILL.md`, `.tree-ring\u002FCLI.md`, or\n  other Tree Ring bridge files.\n\n## How It Works\n\n### Step 1: Discover Local Guidance\n\nCheck whether the current project already has Tree Ring guidance:\n\n```bash\ntest -f .tree-ring\u002FSKILL.md && sed -n '1,220p' .tree-ring\u002FSKILL.md\ntest -f .tree-ring\u002FCLI.md && sed -n '1,220p' .tree-ring\u002FCLI.md\n```\n\nTreat project-local `.tree-ring` files as more authoritative than generic\nexamples in this skill. If the CLI is installed, inspect the current command\nsurface before assuming flags:\n\n```bash\ntree-ring --help\ntree-ring recall --help\ntree-ring remember --help\ntree-ring evidence --help\ntree-ring audit --help\ntree-ring forget --help\n```\n\nIf Tree Ring is not installed, resolve the actual project root and explain the\nexact project-local download before obtaining explicit approval to fetch it.\nDownload the official, version-pinned `v0.15.0\u002Finstall.sh` to a temporary file,\nverify its SHA-256 is\n`ef0d5eb8f09cbe2e4c3abe80ee9a98a56759c89ad4ddd103d6c68314cd653ade`,\ninspect it, then run it. The pinned source is\n`https:\u002F\u002Fraw.githubusercontent.com\u002FTerminallyLazy\u002FTree-Ring-Memory\u002Fv0.15.0\u002Finstall.sh`.\n\n```bash\ncd \u003Cproject-root>\nsh \u003Cverified-installer-path> --project --init --release v0.15.0 --no-animation\n```\n\nDo not pipe a network response directly to a shell. After verification and\ninspection, show the exact installer command and obtain explicit approval again\nbefore executing it. For an installed global CLI, initialize from the project root with\n`tree-ring --root .tree-ring init`; for a project-local CLI, use\n`.tree-ring\u002Fbin\u002Ftree-ring --root .tree-ring init`.\n\nCheck for a newer release without changing files using\n`tree-ring update --check`. Run `tree-ring update` only with user authorization,\nthen rerun `init` in each project root to refresh managed guidance while\npreserving custom content.\n\n## Step 2: Recall Before Risky Work\n\nUse narrow, project-scoped recall first:\n\n```bash\ntree-ring recall \"release behavior\" --project example-service\ntree-ring recall \"sqlite migration\" --project example-service\ntree-ring recall \"user preference\"\n```\n\nUse recalled memory as context, not authority. Verify it against current source\nfiles, tests, docs, issues, pull requests, logs, and runtime state before making\nchanges.\n\n## Step 3: Write Only Durable Memory\n\nWrite concise memory only when it is likely to help future agents:\n\n```bash\ntree-ring remember \"Run project-scoped recall before release changes.\" --event-type lesson --scope project\n```\n\nPrefer specific event types when supported locally:\n\n- `decision`\n- `lesson`\n- `warning`\n- `correction`\n- `user_preference`\n- `tool_result`\n- `summary`\n- `hypothesis`\n\nStore the durable lesson, decision, warning, or follow-up. Do not store the\nfull conversation.\n\n## Step 4: Record Evidence for Evaluated Outcomes\n\nUse evidence records for test runs, incidents, reviewed changes, or other\nevaluated outcomes:\n\n```bash\ntree-ring evidence \\\n  \"Installer smoke test passed in an isolated HOME.\" \\\n  --outcome observed \\\n  --evidence-ref \"ci\u002Finstall-smoke\u002F2026-07-08\"\n```\n\nOutcome guidance:\n\n- `promoted`: durable truth backed by strong evidence\n- `rejected`: failed or rolled-back approach worth keeping visible\n- `deferred`: unresolved idea or future option\n- `observed`: normal evaluated result\n\nDo not promote weak, stale, or unreviewed claims to durable truth.\n\n## Step 5: Use Source Adapters Carefully\n\nWhen a repo has structured source records, run dry runs first:\n\n```bash\ntree-ring dox sync --source-root . --dry-run\ntree-ring revolve sync --source-root revolve --dry-run\ntree-ring integrations scan --source-root .\n```\n\nOnly write adapter summaries when they are concise, source-linked, useful, and\nprivacy-safe. Imported memory does not replace the underlying `AGENTS.md`,\nRevolve record, test, pull request, issue, or documentation.\n\n## Ring Selection\n\nUse the smallest durable ring that fits:\n\n- `cambium`: active or recent task context\n- `outer`: recent decisions and task lessons\n- `inner`: older compressed project knowledge\n- `heartwood`: durable high-confidence truths\n- `scar`: failures, regressions, rejected approaches, warnings\n- `seed`: unresolved ideas, hypotheses, follow-ups\n\nPrefer `outer` or `seed` unless the user confirms durability or the evidence is\nstrong.\n\n## Best Practices\n\n- Recall before risky or repeat work.\n- Keep project memory project-scoped unless it is a durable cross-project user\n  preference.\n- Attach source references such as file paths, issue ids, PR ids, evaluation\n  runs, or docs paths.\n- Re-check current source files and runtime state before acting on recalled\n  memory.\n- Ask at closeout what future agents should remember, avoid, or revisit.\n- Use redaction, deletion, or supersession when memory is wrong, stale,\n  sensitive, or replaced by a newer decision.\n\n## Security & Safety Notes\n\n- Never use Tree Ring Memory as a hidden recorder.\n- Do not store secrets, credentials, tokens, private keys, recovery codes, raw\n  chain-of-thought, or temporary scratchpad content.\n- Do not store sensitive personal data unless the user explicitly asks and the\n  retention boundary is safe.\n- Do not store copyrighted source text beyond short allowed excerpts.\n- Do not run installer, network, destructive, or mutation commands without\n  explicit user approval and a clear target environment.\n- Treat all examples as commands to adapt after checking local `--help`, not as\n  guaranteed command surfaces.\n\n## Limitations\n\n- Tree Ring Memory is not a replacement for source control, issue trackers,\n  documentation, tests, logs, or live runtime verification.\n- Recalled memory can be stale or wrong. Always verify important claims against\n  the current project before using them to make changes.\n- The CLI surface can change across releases. Prefer local `.tree-ring`\n  guidance and `tree-ring --help` over copied command examples.\n- It should not be used for secret storage, comprehensive transcript archives,\n  compliance retention, or unreviewed collection of sensitive personal data.\n- Cross-agent interoperability depends on each tool's ability to call the local\n  CLI or read project-local guidance files.\n\n## Common Pitfalls\n\n- **Problem:** Recalled memory conflicts with current source.\n  **Solution:** Treat source files, tests, docs, and runtime evidence as\n  authoritative; supersede or forget stale memory.\n\n- **Problem:** Memory starts becoming transcript storage.\n  **Solution:** Store only durable decisions, warnings, preferences, outcomes,\n  and follow-ups.\n\n- **Problem:** A lesson is useful but contains sensitive detail.\n  **Solution:** Store a redacted summary or do not store it.\n\n## Related Skills\n\n- `@agent-memory-systems` - Use for broad agent-memory architecture choices.\n- `@agent-memory` - Use for the listed hybrid memory MCP system.\n- `@planning-with-files` - Use when simple persistent files are enough.\n\n## Additional Resources\n\n- Tree Ring Memory repository: \u003Chttps:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002FTree-Ring-Memory>\n- Codex plugin wrapper: \u003Chttps:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002Ftree-ring-memory-codex-plugin>\n",{"name":5,"risk":29,"tags":48,"tools":53,"author":57,"source":33,"license":14,"category":41,"date_added":58,"description":7,"source_repo":59,"source_type":33,"license_source":60},[26,49,50,51,52,38,34],"local-first","recall","privacy","codex",[54,52,55,42,56,35],"claude","cursor","antigravity","TerminallyLazy","2026-07-08","TerminallyLazy\u002FTree-Ring-Memory","https:\u002F\u002Fgithub.com\u002FTerminallyLazy\u002FTree-Ring-Memory\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Ftree-ring-memory","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill tree-ring-memory",{"tool":72,"command":73},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill tree-ring-memory",{"tool":75,"command":76},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill tree-ring-memory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Ftree-ring-memory\u002FSKILL.md",true,[],[81,107,130,152,179,203],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":90,"publishedAt":43},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[91,92,93,94,95,96,83,97,98,99,100,101,33,32,102,29,103,104,105,106],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":43},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[114,115,116,117,34,118,119,120,121,122,123,124,125,101,126,33,127,128,29,129],"delegate","zcode","zcode delegate","review","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":43},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[40,137,138,139,140,52,141,142,143,144,145,146,147,33,32,30,148,149,150,151],"youtube transcript","youtube","safe","github","research","license","https","text","fetch","tooling","clean","output","deepapi","youtube transcripts","blob",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":169,"publishedAt":43},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[158,161,164],{"categoryNo":159,"categoryName":160,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":162,"categoryName":163,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":165,"categoryName":166,"taxonomyType":167,"taxonomyTypeDesc":168},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[40,137,138,170,139,42,140,52,142,171,172,173,174,145,175,33,32,176,177,178],"youtube transcript skills","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":189,"publishedAt":43},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":162,"categoryName":163,"taxonomyType":20,"taxonomyTypeDesc":21},[138,190,191,34,139,192,193,194,195,142,173,196,197,198,199,32,200,30,201,202],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":43},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[209],{"categoryNo":159,"categoryName":160,"taxonomyType":20,"taxonomyTypeDesc":21},[211,138,212,213,139,42,171,214,215,172,173,174,145,216,175,33,32,176,217,150],"youtube full","full","google","server","dlp","credits","automatic"]