[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NVQH6HBSNEKS4RYVF7SMS9":3,"skill-same:01M6NVQH6HBSNEKS4RYVF7SMS9":69},{"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":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":31,"commitSha":51,"skillDirectory":52,"forksCount":13,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":68},"01M6NVQH6HBSNEKS4RYVF7SMS9","artifact-yylo",null,"Capture and retrieve durable YYLO Ledger artifact Records with intentional profiles, payload modes, provenance, retention, and secret-safe immutable evidence.","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\u002Fartifact-yylo\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"artifact yylo","artifact","project","modes","with provenance","inspect","true","profiles","with","retention","records","dev","record","main","community","evidence","never","project-management","provenance","license","2026-11-10 10:12:30",false,"---\nname: artifact-yylo\ndescription: Capture and retrieve durable YYLO Ledger artifact Records with intentional\n  profiles, payload modes, provenance, retention, and secret-safe immutable evidence.\ncategory: project-management\nrisk: safe\nsource: https:\u002F\u002Fgithub.com\u002Fyylo-dev\u002Fyylo-skills\nsource_repo: yylo-dev\u002Fyylo-skills\nsource_type: community\ndate_added: '2026-09-19'\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fyylo-dev\u002Fyylo-skills\u002Fblob\u002Fmain\u002FLICENSE\ncompatibility: Requires the `yy` CLI with the `artifact` record group installed. Captures\n  immutable, secret-safe evidence with provenance and retention; never publishes or\n  deploys.\nargument-hint: '[artifact or evidence to capture\u002Ffind\u002Finspect]'\nenable-shell-directives: true\n---\n\n# Use YYLO artifact Records\n\nTreat Ledger as the source of truth for artifact identity and metadata. Use\n`yy ledger` in a YYLO controller or `yylo-ledger` standalone. Inspect\n`COMMAND artifact --help`; if unavailable, do not create store files manually.\nA Ledger Artifact Record is durable evidence, not an npm\u002FPython release artifact\nand not an implicit request to publish or deploy.\n\n## Classify before capture\n\nChoose the profile matching the evidence:\n\n- `stdout`: bounded process output;\n- `model-output`: an agent\u002Fmodel response;\n- `report`: a generated human- or machine-readable result;\n- `receipt`: evidence binding an operation and its inputs\u002Foutcome.\n\nChoose payload mode deliberately:\n\n- `inline`: small immutable bytes embedded in the Record;\n- `local`: immutable content-addressed bytes in Ledger storage;\n- `external`: immutable external bytes with URI, digest, and size;\n- `link`: URI reference without an immutable-byte guarantee.\n\nPrefer immutable evidence when later verification depends on exact bytes. A link\nmust never be presented as content-addressed proof.\n\n## Create explicitly\n\nUse file\u002Fstdin transport and provide the media type:\n\n```bash\nyy ledger artifact create --title \"Focused test report\" --profile report \\\n  --mode local --media-type application\u002Fjson --file report.json\n```\n\nFor external immutable content, provide the supported URI, SHA-256 digest, and\nsize shown by installed help. Never embed URI credentials. Ledger rejects unsafe\nschemes, traversal, size\u002Fdigest mismatches, oversized capture, and known secret\npatterns.\n\nAttach only supported, non-secret provenance such as actor, agent, model,\nsession, run, invocation, task, or workflow identity. Task\u002Fworkflow provenance\nuses immutable Record IDs. Select `temporary`, `standard`, or `permanent`\nretention deliberately; retention metadata does not itself authorize deletion.\n\n## Operational-document boundary\n\nStore new PDRs, architecture and migration contracts, plans, reports, receipts,\nand execution evidence as Artifact Records. Draft through a fresh external file,\ncapture it with an intentional profile and immutable payload mode, read it back,\nand verify its ID, digest, size, provenance, retention, and history before\nremoving the draft. Use the `report` profile for human-readable PDRs\u002Fcontracts\nunless installed help provides a more specific approved profile.\n\nProduct `docs\u002F` is only for documentation shipped as part of the product. Never\nput operational evidence there to manufacture a task product diff. Preserve\nlegacy `.juno_task\u002Fspecs` files, but do not create new ones as a fallback. If the\ninstalled artifact API is unavailable, stop with the external draft intact and\nrequest a Ledger upgrade; do not put it in task bodies, responses, product docs,\nor manually managed controller paths.\n\n## Find and verify\n\n```bash\nyy ledger artifact search --profile report --projection summary --limit 20 -f json\nyy ledger artifact get RECORD_ID -f json\nyy ledger artifact history RECORD_ID -f ndjson\n```\n\nUse bounded metadata\u002Fsummary projections before requesting payload details.\nVerify profile, mode, media type, digest, size, provenance, retention, revision,\nand immutable ID before relying on evidence.\n\nArtifact payloads are immutable evidence. Represent replacement with explicit\npredecessor\u002Fsuccessor relationships and the installed revision-safe update\ncontract; do not overwrite bytes or edit content objects. Archive is a lifecycle\ntransition, not deletion. Release, publication, external upload, retention\nexecution, and production mutation always require separate authority.\n\n## Complete request\n\n$ARGUMENTS\n\n## When to Use\n\n- You need to capture or retrieve durable YYLO Ledger artifact Records (stdout, model-output, report, receipt) with provenance, retention, and immutable payloads.\n- New operational PDRs, contracts, plans, reports, and receipts belong here - not in product docs, task bodies, or new `.juno_task\u002Fspecs` files.\n\n## Limitations\n\n- Payloads are immutable: represent replacement with predecessor\u002Fsuccessor relations, never by overwriting bytes. Archive is a lifecycle transition, not deletion.\n- Secret-safe only: never embed URI credentials; Ledger rejects unsafe schemes, traversal, size\u002Fdigest mismatches, and known secret patterns.\n- Retention metadata never authorizes deletion; release, publication, upload, and production mutation always need separate authority.\n\n### Example\n\n```bash\nyy ledger artifact search --profile report --projection summary --limit 20 -f json\nyy ledger artifact get RECORD_ID -f json\n```\n\n> Adapted from [yylo-dev\u002Fyylo-skills](https:\u002F\u002Fgithub.com\u002Fyylo-dev\u002Fyylo-skills) (MIT) - v2.0.1; frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance.\n","# Use YYLO artifact Records\n\nTreat Ledger as the source of truth for artifact identity and metadata. Use\n`yy ledger` in a YYLO controller or `yylo-ledger` standalone. Inspect\n`COMMAND artifact --help`; if unavailable, do not create store files manually.\nA Ledger Artifact Record is durable evidence, not an npm\u002FPython release artifact\nand not an implicit request to publish or deploy.\n\n## Classify before capture\n\nChoose the profile matching the evidence:\n\n- `stdout`: bounded process output;\n- `model-output`: an agent\u002Fmodel response;\n- `report`: a generated human- or machine-readable result;\n- `receipt`: evidence binding an operation and its inputs\u002Foutcome.\n\nChoose payload mode deliberately:\n\n- `inline`: small immutable bytes embedded in the Record;\n- `local`: immutable content-addressed bytes in Ledger storage;\n- `external`: immutable external bytes with URI, digest, and size;\n- `link`: URI reference without an immutable-byte guarantee.\n\nPrefer immutable evidence when later verification depends on exact bytes. A link\nmust never be presented as content-addressed proof.\n\n## Create explicitly\n\nUse file\u002Fstdin transport and provide the media type:\n\n```bash\nyy ledger artifact create --title \"Focused test report\" --profile report \\\n  --mode local --media-type application\u002Fjson --file report.json\n```\n\nFor external immutable content, provide the supported URI, SHA-256 digest, and\nsize shown by installed help. Never embed URI credentials. Ledger rejects unsafe\nschemes, traversal, size\u002Fdigest mismatches, oversized capture, and known secret\npatterns.\n\nAttach only supported, non-secret provenance such as actor, agent, model,\nsession, run, invocation, task, or workflow identity. Task\u002Fworkflow provenance\nuses immutable Record IDs. Select `temporary`, `standard`, or `permanent`\nretention deliberately; retention metadata does not itself authorize deletion.\n\n## Operational-document boundary\n\nStore new PDRs, architecture and migration contracts, plans, reports, receipts,\nand execution evidence as Artifact Records. Draft through a fresh external file,\ncapture it with an intentional profile and immutable payload mode, read it back,\nand verify its ID, digest, size, provenance, retention, and history before\nremoving the draft. Use the `report` profile for human-readable PDRs\u002Fcontracts\nunless installed help provides a more specific approved profile.\n\nProduct `docs\u002F` is only for documentation shipped as part of the product. Never\nput operational evidence there to manufacture a task product diff. Preserve\nlegacy `.juno_task\u002Fspecs` files, but do not create new ones as a fallback. If the\ninstalled artifact API is unavailable, stop with the external draft intact and\nrequest a Ledger upgrade; do not put it in task bodies, responses, product docs,\nor manually managed controller paths.\n\n## Find and verify\n\n```bash\nyy ledger artifact search --profile report --projection summary --limit 20 -f json\nyy ledger artifact get RECORD_ID -f json\nyy ledger artifact history RECORD_ID -f ndjson\n```\n\nUse bounded metadata\u002Fsummary projections before requesting payload details.\nVerify profile, mode, media type, digest, size, provenance, retention, revision,\nand immutable ID before relying on evidence.\n\nArtifact payloads are immutable evidence. Represent replacement with explicit\npredecessor\u002Fsuccessor relationships and the installed revision-safe update\ncontract; do not overwrite bytes or edit content objects. Archive is a lifecycle\ntransition, not deletion. Release, publication, external upload, retention\nexecution, and production mutation always require separate authority.\n\n## Complete request\n\n$ARGUMENTS\n\n## When to Use\n\n- You need to capture or retrieve durable YYLO Ledger artifact Records (stdout, model-output, report, receipt) with provenance, retention, and immutable payloads.\n- New operational PDRs, contracts, plans, reports, and receipts belong here - not in product docs, task bodies, or new `.juno_task\u002Fspecs` files.\n\n## Limitations\n\n- Payloads are immutable: represent replacement with predecessor\u002Fsuccessor relations, never by overwriting bytes. Archive is a lifecycle transition, not deletion.\n- Secret-safe only: never embed URI credentials; Ledger rejects unsafe schemes, traversal, size\u002Fdigest mismatches, and known secret patterns.\n- Retention metadata never authorizes deletion; release, publication, upload, and production mutation always need separate authority.\n\n### Example\n\n```bash\nyy ledger artifact search --profile report --projection summary --limit 20 -f json\nyy ledger artifact get RECORD_ID -f json\n```\n\n> Adapted from [yylo-dev\u002Fyylo-skills](https:\u002F\u002Fgithub.com\u002Fyylo-dev\u002Fyylo-skills) (MIT) - v2.0.1; frontmatter, When to Use\u002FLimitations, and safety boundaries added for upstream compliance.\n",{"name":5,"risk":43,"source":44,"license":14,"category":35,"date_added":45,"description":7,"source_repo":46,"source_type":32,"argument-hint":47,"compatibility":48,"license_source":49,"enable-shell-directives":50},"safe","https:\u002F\u002Fgithub.com\u002Fyylo-dev\u002Fyylo-skills","2026-09-19","yylo-dev\u002Fyylo-skills","[artifact or evidence to capture\u002Ffind\u002Finspect]","Requires the `yy` CLI with the `artifact` record group installed. Captures immutable, secret-safe evidence with provenance and retention; never publishes or deploys.","https:\u002F\u002Fgithub.com\u002Fyylo-dev\u002Fyylo-skills\u002Fblob\u002Fmain\u002FLICENSE",true,"f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fartifact-yylo","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":57,"prompt":67,"zipAvailable":50},[58,61,64],{"tool":59,"command":60},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill artifact-yylo",{"tool":62,"command":63},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill artifact-yylo",{"tool":65,"command":66},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill artifact-yylo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fartifact-yylo\u002FSKILL.md",[],[70,99,123,146,174,198],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":38},"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",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[82,83,84,85,86,87,72,88,89,90,91,92,32,31,93,94,95,96,97,98],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","critical","scope","scripts","relevant","implementing",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":38},"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",[],[106,107,108,109,110,111,112,113,114,115,116,117,118,92,119,32,120,121,94,122],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":38},"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",[],[130,131,132,43,133,134,135,37,136,137,138,139,140,32,31,141,142,143,144,145],"transcript","youtube transcript","youtube","github","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":163,"publishedAt":38},"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",[152,155,158],{"categoryNo":153,"categoryName":154,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":156,"categoryName":157,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":159,"categoryName":160,"taxonomyType":161,"taxonomyTypeDesc":162},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[130,131,132,164,43,165,133,134,37,166,167,168,169,138,170,32,31,171,172,173],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":184,"publishedAt":38},"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",[180,183],{"categoryNo":181,"categoryName":182,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":156,"categoryName":157,"taxonomyType":79,"taxonomyTypeDesc":80},[132,185,186,110,43,187,188,189,190,37,168,191,192,193,194,31,195,141,196,197],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":205,"publishedAt":38},"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",[204],{"categoryNo":153,"categoryName":154,"taxonomyType":79,"taxonomyTypeDesc":80},[206,132,207,208,43,165,166,209,210,167,168,169,138,211,170,32,31,171,212,144],"youtube full","full","google","server","dlp","credits","automatic"]