[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PZNGV78ZCBCJFBP1R833CD":3,"skill-same:01M6PZNGV78ZCBCJFBP1R833CD":77},{"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":33,"commitSha":58,"skillDirectory":59,"forksCount":13,"repositoryHtmlUrl":60,"repositoryHomepageUrl":6,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":62,"install":63,"resources":76},"01M6PZNGV78ZCBCJFBP1R833CD","trading-ledger",null,"A trading journal that captures the decision, not just the fill: thesis, plan, and emotion at the moment of entry, written to the user's own Notion database; reviews grade decisions, not P&L.","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\u002Ftrading-ledger\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"ledger","trading ledger","trading","community","at","reviews","critical","journal","thesis","decision-making","main","notion","Market","decisions","just","decision","journaling","plan","license","database","2026-11-10 10:12:30",false,"---\nname: trading-ledger\ndescription: \"A trading journal that captures the decision, not just the fill: thesis, plan, and emotion at the moment of entry, written to the user's own Notion database; reviews grade decisions, not P&L.\"\ncategory: productivity\nrisk: critical\nsource: community\nsource_repo: cruisekkk\u002Ftrading-ledger\nsource_type: community\ndate_added: \"2026-07-04\"\nauthor: cruisekkk\ntags: [trading-journal, notion, journaling, market-wizards, decision-making]\ntools: [claude]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fcruisekkk\u002Ftrading-ledger\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# Trading Ledger\n\n## Overview\n\nA journaling skill in the tradition of the *Market Wizards* interviews: a written record of every trade's decision process, reviewed on a schedule. The user reports a trade in plain language — *\"bought 500 NVDA at 135, stop at 128, betting the post-earnings dip fills\"* — and the agent writes ticker, size, and price to the user's own Notion database **plus the part every spreadsheet journal loses: the thesis, the plan, and the emotion.** If no reason is stated, it asks on the spot, because entry reasons decay overnight. Reviews grade decision quality against the user's own plan — a per-plan loss scores better than a lucky win. Core contract: never fabricate when unsure; mark `To-confirm` and batch-ask.\n\n## When to Use This Skill\n\n- Use when the user reports a trade fill (\"bought 500 NVDA at 135\", \"closed my TSLA position\", \"opened 2 ES contracts short\")\n- Use when the user says \"log a trade\" or \"trading ledger\", or \"tidy up my trading ledger\"\n- Use when the user asks to \"review my trades\"\n\n## How It Works\n\n### Step 1: Confirm the database (first use per session)\n\nUse Notion `search` to find candidate **databases** (type `database`, not pages) whose title\ncontains **\"trading-ledger\"**. Before any `query` or `create-pages` call, show the user the\ncandidate title and `data_source_id` (`collection:\u002F\u002F...` UUID) and ask them to confirm the exact\ndatabase for this session. A single title match is not sufficient confirmation. If the connector\nreturns owner or schema metadata, show it as an additional identity check. Use only the\nuser-confirmed ID for the remainder of the session; do not re-run fuzzy selection after a\nconfirmation.\n\nThe companion Notion template (free, linked in the source repo) ships this schema — select values are a controlled enum, copy them exactly:\n\n- `Entry` (title); `Ticker` (text — strikes\u002Fexpiries here: NVDA \u002F NVDA 0620C150 \u002F ESU6)\n- `Market` (select): US Stocks \u002F US Options \u002F US Futures \u002F A-Shares \u002F HK Stocks \u002F CN Futures \u002F Crypto \u002F Other\n- `Direction` (select): Long \u002F Short · `Size` (text, with units)\n- `Entry Price` \u002F `Exit Price` (number) · `Entry Date` \u002F `Exit Date` (date — expand to `\"date:Entry Date:start\": \"YYYY-MM-DD\"`; a bare value fails with HTTP 400)\n- `Thesis` (text) — **the soul of the journal; if missing, ask on the spot**\n- `Plan` (text) — stop \u002F target \u002F contingency; ask if missing\n- `Emotion` (select): Calm \u002F FOMO \u002F Panic \u002F Revenge \u002F Boredom \u002F Overconfidence — tag only what the user admits or what is plain in their words; don't diagnose\n- `Execution` (select): Per plan \u002F Early exit \u002F Delayed stop \u002F Impulse \u002F Unplanned add — filled at close\n- `P&L` (number, realized) · `Status` (select): Open \u002F Closed \u002F To-confirm \u002F Reviewed · `Review` (text) · `Notes` (text)\n\n### Step 2: Opening a trade\n\nParse → create a row with `Status=Open`. A missing thesis is the one field worth interrupting for — ask immediately. Anything else uncertain: record what you have, put the question in `Notes`, mark `To-confirm`.\n\n### Step 3: Closing or adjusting\n\nFind that ticker's `Status=Open` row → fill Exit Price \u002F Exit Date \u002F P&L \u002F Execution → set `Closed`. Grade `Execution` against the user's own `Plan`: stopped where planned = Per plan; ran before the target = Early exit; held through the stop = Delayed stop. No matching open row → create one marked `To-confirm` and ask whether the entry was never logged.\n\n### Step 4: Batch reconcile and review\n\n- \"tidy up my trading ledger\" → query `Status=To-confirm` rows → collect **all** open questions into one message.\n- \"review my trades\" → query recent `Closed` + all `Open` rows. For each closed trade, three questions: **Did the thesis play out?** (wrong thesis + profit = luck — say so). **How was the execution?** (a per-plan loss is a good trade). **What share of trades were emotion-tagged?** Write conclusions into `Review`, move `Closed` → `Reviewed`, and for every open position ask: *does the entry thesis still hold today?*\n\nParsing rules: infer `Market` from symbol and context (ambiguous → ask); bought put = Short exposure + note it is a long put; record only given prices\u002Fsizes — **never look up market prices to fill gaps**; \"today\" = the user's local trading date — confirm before writing.\n\n## Examples\n\n### Example 1: Opening with a missing plan\n\n```text\nUser:  picked up some TSM July calls this morning, same thesis as before earnings\nAgent: Logged ✅ TSM July calls · Long · Open\n       ❓ To-confirm: which strike\u002Fexpiry, how many contracts, at what price?\n       ❓ And the plan — holding through earnings, or is there a stop?\nUser:  0731 475C, 1 contract at 18.50, holding to earnings\nAgent: Updated ✅ Ticker: TSM 0731C475 · Thesis: pre-earnings run-up · Plan: hold through earnings\n```\n\n### Example 2: Review day\n\n```text\nUser:  review my trades\nAgent: 3 closed since last review:\n       · NVDA long — thesis played out, exited per plan. Good trade.\n       · TSLA short — thesis wrong, but stopped exactly where planned. Good trade, bad outcome.\n       · SPY calls — profitable, but Entry was tagged FOMO and there was no plan. Lucky, not good.\n       Open positions: TSM call — earnings run-up thesis still holds until the 7\u002F29 print.\n```\n\n## Best Practices\n\n- ✅ Ask for the thesis at entry time — it decays overnight and memory flatters\n- ✅ Grade execution against the user's own plan, never against hindsight\n- ✅ Batch all questions into one message; give a short receipt after logging\n- ❌ Don't compute P&L you are unsure of — options and futures have multipliers; use the user's numbers\n- ❌ Don't invent select values; copy the enum\n- ❌ A review is not a P&L total — it grades thesis and execution\n\n## Limitations\n\n- Requires the user's own Notion workspace, the companion database (duplicate the template from the source repo), and the official Notion connector granted access — connector\u002Fskill setups currently live on paid Claude tiers.\n- Close, reconcile, and review flows require reliable Notion database query\u002Fsearch access to open, closed, and `To-confirm` rows. If the connector cannot query the ledger, stop after logging the user's new facts and ask them to provide the relevant row details instead of guessing matches.\n- No broker integration, by design: the broker knows the fills; only the user knows the reasons. The user must self-report.\n- Grading honesty depends on input honesty: a thesis backfilled three days later defeats the point (the skill nags, but cannot prevent it).\n\n## Security & Safety Notes\n\n- **Mutation scope**: writes and updates rows only in the exact Notion database ID confirmed by\n  the user for the current session via the official Notion connector (MCP) — no shell commands,\n  no network fetches, no market-data lookups, no credentials.\n- **This skill must never produce trading signals, price data, or buy\u002Fsell recommendations.** It records and mirrors the user's own decisions; the review asks questions, it does not advise. Nothing it writes is financial advice, and it should say so if asked for a recommendation.\n- On claude.ai, Notion's write tools default to *needs approval* — the first write pops an approval prompt; expected, not a hang.\n\n## Common Pitfalls\n\n- **Problem:** Notion API 400 on date fields.\n  **Solution:** Expand to `\"date:Entry Date:start\": \"YYYY-MM-DD\"`.\n- **Problem:** `create-pages` succeeds but the date column is empty (known Notion MCP issue: [notion-mcp-server#121](https:\u002F\u002Fgithub.com\u002Fmakenotion\u002Fnotion-mcp-server\u002Fissues\u002F121) — expanded date fields silently dropped).\n  **Solution:** After the session's first create, read the row back; if the date is empty, fill it with `update-page`.\n- **Problem:** Close matched to the wrong row when the same ticker was traded twice.\n  **Solution:** Match on `Status=Open` + ticker; if multiple open rows match, ask which one.\n- **Problem:** Overnight US fills dated to the wrong day for non-US users.\n  **Solution:** Overnight fills belong to the US trading date; confirm the date before writing.\n\n## Related Skills\n\n- `@time-ledger` - The same \"parse plain language → own Notion DB → ask instead of guessing\" pattern applied to time tracking.\n","# Trading Ledger\n\n## Overview\n\nA journaling skill in the tradition of the *Market Wizards* interviews: a written record of every trade's decision process, reviewed on a schedule. The user reports a trade in plain language — *\"bought 500 NVDA at 135, stop at 128, betting the post-earnings dip fills\"* — and the agent writes ticker, size, and price to the user's own Notion database **plus the part every spreadsheet journal loses: the thesis, the plan, and the emotion.** If no reason is stated, it asks on the spot, because entry reasons decay overnight. Reviews grade decision quality against the user's own plan — a per-plan loss scores better than a lucky win. Core contract: never fabricate when unsure; mark `To-confirm` and batch-ask.\n\n## When to Use This Skill\n\n- Use when the user reports a trade fill (\"bought 500 NVDA at 135\", \"closed my TSLA position\", \"opened 2 ES contracts short\")\n- Use when the user says \"log a trade\" or \"trading ledger\", or \"tidy up my trading ledger\"\n- Use when the user asks to \"review my trades\"\n\n## How It Works\n\n### Step 1: Confirm the database (first use per session)\n\nUse Notion `search` to find candidate **databases** (type `database`, not pages) whose title\ncontains **\"trading-ledger\"**. Before any `query` or `create-pages` call, show the user the\ncandidate title and `data_source_id` (`collection:\u002F\u002F...` UUID) and ask them to confirm the exact\ndatabase for this session. A single title match is not sufficient confirmation. If the connector\nreturns owner or schema metadata, show it as an additional identity check. Use only the\nuser-confirmed ID for the remainder of the session; do not re-run fuzzy selection after a\nconfirmation.\n\nThe companion Notion template (free, linked in the source repo) ships this schema — select values are a controlled enum, copy them exactly:\n\n- `Entry` (title); `Ticker` (text — strikes\u002Fexpiries here: NVDA \u002F NVDA 0620C150 \u002F ESU6)\n- `Market` (select): US Stocks \u002F US Options \u002F US Futures \u002F A-Shares \u002F HK Stocks \u002F CN Futures \u002F Crypto \u002F Other\n- `Direction` (select): Long \u002F Short · `Size` (text, with units)\n- `Entry Price` \u002F `Exit Price` (number) · `Entry Date` \u002F `Exit Date` (date — expand to `\"date:Entry Date:start\": \"YYYY-MM-DD\"`; a bare value fails with HTTP 400)\n- `Thesis` (text) — **the soul of the journal; if missing, ask on the spot**\n- `Plan` (text) — stop \u002F target \u002F contingency; ask if missing\n- `Emotion` (select): Calm \u002F FOMO \u002F Panic \u002F Revenge \u002F Boredom \u002F Overconfidence — tag only what the user admits or what is plain in their words; don't diagnose\n- `Execution` (select): Per plan \u002F Early exit \u002F Delayed stop \u002F Impulse \u002F Unplanned add — filled at close\n- `P&L` (number, realized) · `Status` (select): Open \u002F Closed \u002F To-confirm \u002F Reviewed · `Review` (text) · `Notes` (text)\n\n### Step 2: Opening a trade\n\nParse → create a row with `Status=Open`. A missing thesis is the one field worth interrupting for — ask immediately. Anything else uncertain: record what you have, put the question in `Notes`, mark `To-confirm`.\n\n### Step 3: Closing or adjusting\n\nFind that ticker's `Status=Open` row → fill Exit Price \u002F Exit Date \u002F P&L \u002F Execution → set `Closed`. Grade `Execution` against the user's own `Plan`: stopped where planned = Per plan; ran before the target = Early exit; held through the stop = Delayed stop. No matching open row → create one marked `To-confirm` and ask whether the entry was never logged.\n\n### Step 4: Batch reconcile and review\n\n- \"tidy up my trading ledger\" → query `Status=To-confirm` rows → collect **all** open questions into one message.\n- \"review my trades\" → query recent `Closed` + all `Open` rows. For each closed trade, three questions: **Did the thesis play out?** (wrong thesis + profit = luck — say so). **How was the execution?** (a per-plan loss is a good trade). **What share of trades were emotion-tagged?** Write conclusions into `Review`, move `Closed` → `Reviewed`, and for every open position ask: *does the entry thesis still hold today?*\n\nParsing rules: infer `Market` from symbol and context (ambiguous → ask); bought put = Short exposure + note it is a long put; record only given prices\u002Fsizes — **never look up market prices to fill gaps**; \"today\" = the user's local trading date — confirm before writing.\n\n## Examples\n\n### Example 1: Opening with a missing plan\n\n```text\nUser:  picked up some TSM July calls this morning, same thesis as before earnings\nAgent: Logged ✅ TSM July calls · Long · Open\n       ❓ To-confirm: which strike\u002Fexpiry, how many contracts, at what price?\n       ❓ And the plan — holding through earnings, or is there a stop?\nUser:  0731 475C, 1 contract at 18.50, holding to earnings\nAgent: Updated ✅ Ticker: TSM 0731C475 · Thesis: pre-earnings run-up · Plan: hold through earnings\n```\n\n### Example 2: Review day\n\n```text\nUser:  review my trades\nAgent: 3 closed since last review:\n       · NVDA long — thesis played out, exited per plan. Good trade.\n       · TSLA short — thesis wrong, but stopped exactly where planned. Good trade, bad outcome.\n       · SPY calls — profitable, but Entry was tagged FOMO and there was no plan. Lucky, not good.\n       Open positions: TSM call — earnings run-up thesis still holds until the 7\u002F29 print.\n```\n\n## Best Practices\n\n- ✅ Ask for the thesis at entry time — it decays overnight and memory flatters\n- ✅ Grade execution against the user's own plan, never against hindsight\n- ✅ Batch all questions into one message; give a short receipt after logging\n- ❌ Don't compute P&L you are unsure of — options and futures have multipliers; use the user's numbers\n- ❌ Don't invent select values; copy the enum\n- ❌ A review is not a P&L total — it grades thesis and execution\n\n## Limitations\n\n- Requires the user's own Notion workspace, the companion database (duplicate the template from the source repo), and the official Notion connector granted access — connector\u002Fskill setups currently live on paid Claude tiers.\n- Close, reconcile, and review flows require reliable Notion database query\u002Fsearch access to open, closed, and `To-confirm` rows. If the connector cannot query the ledger, stop after logging the user's new facts and ask them to provide the relevant row details instead of guessing matches.\n- No broker integration, by design: the broker knows the fills; only the user knows the reasons. The user must self-report.\n- Grading honesty depends on input honesty: a thesis backfilled three days later defeats the point (the skill nags, but cannot prevent it).\n\n## Security & Safety Notes\n\n- **Mutation scope**: writes and updates rows only in the exact Notion database ID confirmed by\n  the user for the current session via the official Notion connector (MCP) — no shell commands,\n  no network fetches, no market-data lookups, no credentials.\n- **This skill must never produce trading signals, price data, or buy\u002Fsell recommendations.** It records and mirrors the user's own decisions; the review asks questions, it does not advise. Nothing it writes is financial advice, and it should say so if asked for a recommendation.\n- On claude.ai, Notion's write tools default to *needs approval* — the first write pops an approval prompt; expected, not a hang.\n\n## Common Pitfalls\n\n- **Problem:** Notion API 400 on date fields.\n  **Solution:** Expand to `\"date:Entry Date:start\": \"YYYY-MM-DD\"`.\n- **Problem:** `create-pages` succeeds but the date column is empty (known Notion MCP issue: [notion-mcp-server#121](https:\u002F\u002Fgithub.com\u002Fmakenotion\u002Fnotion-mcp-server\u002Fissues\u002F121) — expanded date fields silently dropped).\n  **Solution:** After the session's first create, read the row back; if the date is empty, fill it with `update-page`.\n- **Problem:** Close matched to the wrong row when the same ticker was traded twice.\n  **Solution:** Match on `Status=Open` + ticker; if multiple open rows match, ask which one.\n- **Problem:** Overnight US fills dated to the wrong day for non-US users.\n  **Solution:** Overnight fills belong to the US trading date; confirm the date before writing.\n\n## Related Skills\n\n- `@time-ledger` - The same \"parse plain language → own Notion DB → ask instead of guessing\" pattern applied to time tracking.\n",{"name":5,"risk":29,"tags":48,"tools":51,"author":53,"source":26,"license":14,"category":54,"date_added":55,"description":7,"source_repo":56,"source_type":26,"license_source":57},[49,34,39,50,32],"trading-journal","market-wizards",[52],"claude","cruisekkk","productivity","2026-07-04","cruisekkk\u002Ftrading-ledger","https:\u002F\u002Fgithub.com\u002Fcruisekkk\u002Ftrading-ledger\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Ftrading-ledger","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":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill trading-ledger",{"tool":69,"command":70},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill trading-ledger",{"tool":72,"command":73},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill trading-ledger","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Ftrading-ledger\u002FSKILL.md",true,[],[78,104,128,152,178,202],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":87,"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",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[88,89,90,91,92,93,80,94,95,96,97,98,26,33,99,29,100,101,102,103],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"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",[],[111,112,113,114,115,116,117,118,119,120,121,122,123,98,124,26,125,126,29,127],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"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",[],[135,136,137,138,139,140,141,41,142,143,144,145,146,26,33,147,148,149,150,151],"transcript","youtube transcript","youtube","safe","github","codex","research","https","text","fetch","tooling","clean","local","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":167,"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,159,162],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":160,"categoryName":161,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":163,"categoryName":164,"taxonomyType":165,"taxonomyTypeDesc":166},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[135,136,137,168,138,169,139,140,41,170,171,172,173,144,174,26,33,175,176,177],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":188,"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",[184,187],{"categoryNo":185,"categoryName":186,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":160,"categoryName":161,"taxonomyType":20,"taxonomyTypeDesc":21},[137,189,190,115,138,191,192,193,194,41,172,195,196,197,198,33,199,147,200,201],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":209,"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",[208],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[210,137,211,212,138,169,170,213,214,171,172,173,144,215,174,26,33,175,216,150],"youtube full","full","google","server","dlp","credits","automatic"]