[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FD9F7FPFWFQN86TGAEEGNM":3,"skill-same:01M6FD9F7FPFWFQN86TGAEEGNM":83},{"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":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":35,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":69,"install":70,"resources":82},"01M6FD9F7FPFWFQN86TGAEEGNM","wiki-yylo",null,"Use YYLO Ledger wiki Records as durable project knowledge. Search before creating, classify information correctly, and make revision-safe Markdown updates without editing Ledger storage directly.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",13,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-wiki-yylo\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"wiki yylo","wiki","never","updates","standalone","with","information","records","as","classify","project","project knowledge","main","community","only","cli","use","question","editing","project-management","knowledge","markdown","controller","search","license","dev","update","create","2026-11-10 10:12:30",false,"---\nname: wiki-yylo\ndescription: Use YYLO Ledger wiki Records as durable project knowledge. Search before\n  creating, classify information correctly, and make revision-safe Markdown updates\n  without editing Ledger storage directly.\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 `wiki` record group installed (controller\n  or standalone). Revision-safe Markdown updates only; never edit Ledger storage directly.\nargument-hint: '[wiki question or knowledge to find\u002Fcreate\u002Fupdate]'\nenable-shell-directives: true\n---\n\n# Use YYLO wiki Records\n\nTreat Ledger as the source of truth. Use `yy ledger` in a YYLO controller and\n`yylo-ledger` in a standalone Ledger project. Inspect `COMMAND wiki --help` before\nacting; if `wiki` is absent, the installed Ledger version does not expose native\nRecord commands and must not be bypassed with direct file edits.\n\n## Choose the right record\n\nBefore writing, decide where the information belongs:\n\n- **Wiki**: durable explanatory project or domain knowledge that future work must discover.\n- **Task**: scoped requested work, status, dependencies, acceptance criteria, and completion evidence.\n- **Workflow**: validated structured steps, not prose guidance.\n- **Artifact**: generated evidence, reports, receipts, logs, model output, or binary payloads.\n- **Source documentation**: documentation released and versioned with product code.\n\nDo not put secrets, caches, session transcripts, temporary status, bulky generated\nevidence, or owner-only operational receipts in a wiki.\n\n## Discover before creating\n\nUse bounded summary searches first. Resolve records by immutable ID whenever one\nis known; slugs and aliases are discovery conveniences, not replacement identity.\n\n```bash\nyy ledger wiki search --text \"deployment policy\" --projection summary --limit 20 -f json\nyy ledger wiki get RECORD_ID -f json\nyy ledger wiki get RECORD_ID --raw\n```\n\nUse `--scope archive|all` only when the request requires cold records. Request\n`full` projection only when payload bytes are necessary.\n\n## Create durable Markdown\n\nUse a file or stdin for substantial or shell-sensitive content:\n\n```bash\nyy ledger wiki create --title \"Service ownership\" --file ownership.md\nyy ledger wiki create --title \"Incident notes\" --file - \u003C incident-notes.md\n```\n\nChoose a stable title, namespace, slug, aliases, and relations deliberately. Keep\none topic per Record and link related immutable Record IDs rather than duplicating\ntruth.\n\n## Update safely\n\n1. Read the current Record and revision.\n2. Preserve its immutable ID and inspect history when intent is unclear.\n3. Follow `wiki update --help` for the installed compare-and-replace controls.\n4. Supply the expected revision and required preimage\u002Fdigest evidence.\n5. Use file transport; do not rewrite Ledger files yourself.\n6. Read back the resulting revision and receipt.\n\nA revision or preimage mismatch means the source changed: reread and reconcile.\nNever force past concurrent edits. Archive is a lifecycle transition, not delete.\n\nUse `--front-matter` only for canonical front-matter interchange and `--rendered`\nfor inert, HTML-escaped rendering. Use `history RECORD_ID` to understand revisions;\ndo not infer history from the latest payload alone.\n\n## Project wiki boundary\n\nPortable controller guidance may live under the controller wiki, while project\nand domain pages retain project-owned paths. Package-managed and project-owned\npages can coexist. Migration, runtime replacement, exceptional merge recovery,\nrelease, deployment, and cold-archive maintenance remain authoritative runbooks,\nnot content to summarize into an everyday global skill.\n\n## Complete request\n\n$ARGUMENTS\n\n## When to Use\n\n- You need durable project or domain knowledge as YYLO Ledger wiki Records (search, create, revision-safe update).\n- You must first decide the record belongs in the wiki rather than a task, workflow, artifact, or product docs.\n\n## Limitations\n\n- Search before creating; one topic per Record, linked by immutable Record IDs.\n- Never store secrets, caches, session transcripts, temporary status, bulky generated evidence, or owner-only receipts in a wiki.\n- Updates bind to the expected revision\u002Fpreimage; on mismatch reread and reconcile - never force past concurrent edits. Archive is a lifecycle transition, not deletion.\n- If the `wiki` group is absent, fail closed and request a Ledger upgrade.\n\n### Example\n\n```bash\nyy ledger wiki search --text \"deployment policy\" --projection summary --limit 20 -f json\nyy ledger wiki 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 wiki Records\n\nTreat Ledger as the source of truth. Use `yy ledger` in a YYLO controller and\n`yylo-ledger` in a standalone Ledger project. Inspect `COMMAND wiki --help` before\nacting; if `wiki` is absent, the installed Ledger version does not expose native\nRecord commands and must not be bypassed with direct file edits.\n\n## Choose the right record\n\nBefore writing, decide where the information belongs:\n\n- **Wiki**: durable explanatory project or domain knowledge that future work must discover.\n- **Task**: scoped requested work, status, dependencies, acceptance criteria, and completion evidence.\n- **Workflow**: validated structured steps, not prose guidance.\n- **Artifact**: generated evidence, reports, receipts, logs, model output, or binary payloads.\n- **Source documentation**: documentation released and versioned with product code.\n\nDo not put secrets, caches, session transcripts, temporary status, bulky generated\nevidence, or owner-only operational receipts in a wiki.\n\n## Discover before creating\n\nUse bounded summary searches first. Resolve records by immutable ID whenever one\nis known; slugs and aliases are discovery conveniences, not replacement identity.\n\n```bash\nyy ledger wiki search --text \"deployment policy\" --projection summary --limit 20 -f json\nyy ledger wiki get RECORD_ID -f json\nyy ledger wiki get RECORD_ID --raw\n```\n\nUse `--scope archive|all` only when the request requires cold records. Request\n`full` projection only when payload bytes are necessary.\n\n## Create durable Markdown\n\nUse a file or stdin for substantial or shell-sensitive content:\n\n```bash\nyy ledger wiki create --title \"Service ownership\" --file ownership.md\nyy ledger wiki create --title \"Incident notes\" --file - \u003C incident-notes.md\n```\n\nChoose a stable title, namespace, slug, aliases, and relations deliberately. Keep\none topic per Record and link related immutable Record IDs rather than duplicating\ntruth.\n\n## Update safely\n\n1. Read the current Record and revision.\n2. Preserve its immutable ID and inspect history when intent is unclear.\n3. Follow `wiki update --help` for the installed compare-and-replace controls.\n4. Supply the expected revision and required preimage\u002Fdigest evidence.\n5. Use file transport; do not rewrite Ledger files yourself.\n6. Read back the resulting revision and receipt.\n\nA revision or preimage mismatch means the source changed: reread and reconcile.\nNever force past concurrent edits. Archive is a lifecycle transition, not delete.\n\nUse `--front-matter` only for canonical front-matter interchange and `--rendered`\nfor inert, HTML-escaped rendering. Use `history RECORD_ID` to understand revisions;\ndo not infer history from the latest payload alone.\n\n## Project wiki boundary\n\nPortable controller guidance may live under the controller wiki, while project\nand domain pages retain project-owned paths. Package-managed and project-owned\npages can coexist. Migration, runtime replacement, exceptional merge recovery,\nrelease, deployment, and cold-archive maintenance remain authoritative runbooks,\nnot content to summarize into an everyday global skill.\n\n## Complete request\n\n$ARGUMENTS\n\n## When to Use\n\n- You need durable project or domain knowledge as YYLO Ledger wiki Records (search, create, revision-safe update).\n- You must first decide the record belongs in the wiki rather than a task, workflow, artifact, or product docs.\n\n## Limitations\n\n- Search before creating; one topic per Record, linked by immutable Record IDs.\n- Never store secrets, caches, session transcripts, temporary status, bulky generated evidence, or owner-only receipts in a wiki.\n- Updates bind to the expected revision\u002Fpreimage; on mismatch reread and reconcile - never force past concurrent edits. Archive is a lifecycle transition, not deletion.\n- If the `wiki` group is absent, fail closed and request a Ledger upgrade.\n\n### Example\n\n```bash\nyy ledger wiki search --text \"deployment policy\" --projection summary --limit 20 -f json\nyy ledger wiki 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":56,"source":57,"license":14,"category":42,"date_added":58,"description":7,"source_repo":59,"source_type":36,"argument-hint":60,"compatibility":61,"license_source":62,"enable-shell-directives":63},"safe","https:\u002F\u002Fgithub.com\u002Fyylo-dev\u002Fyylo-skills","2026-09-19","yylo-dev\u002Fyylo-skills","[wiki question or knowledge to find\u002Fcreate\u002Fupdate]","Requires the `yy` CLI with the `wiki` record group installed (controller or standalone). Revision-safe Markdown updates only; never edit Ledger storage directly.","https:\u002F\u002Fgithub.com\u002Fyylo-dev\u002Fyylo-skills\u002Fblob\u002Fmain\u002FLICENSE",true,"7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-wiki-yylo",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-14 14:18:11",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":63},[72,75,78],{"tool":73,"command":74},"npx","npx skills add boisenoise\u002Fskills-collections --skill wiki-yylo",{"tool":76,"command":77},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill wiki-yylo",{"tool":79,"command":80},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill wiki-yylo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-wiki-yylo\u002FSKILL.md",[],[84,112,134,160,179,201],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":51},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[93,94,95,96,97,98,46,99,100,101,102,37,103,104,105,106,107,108,109,110,111],"web","access","web access","official","development","browser","data","Tools","read","fetch","youtube","free tools","platform","critical","free","cover","normal","when","2026",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":122,"publishedAt":51},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[114,123,38,124,96,97,47,100,125,126,127,128,39,129,130,106,131,28,132,133,111],"MCP","github","Budget","credentials","team","catalog","call","discover","external tools","scoped","blob",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":146,"publishedAt":51},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[141],{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[136,124,96,47,147,148,149,150,151,152,106,153,154,155,28,156,157,158,159,133,114,111],"https","email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":51},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[168,169,170,124,96,47,171,172,147,173,125,174,175,176,151,106,177,178,133,114,111],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"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":88,"licenseFileUrl":183,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":51},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[187,188,124,189,96,50,47,190,191,192,193,194,106,195,196,197,198,199,200,133],"make","make ugc","research","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":88,"licenseFileUrl":205,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":51},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[209,210,211,124,96,47,212,213,150,214,31,106,215,216,217,29,218,219,220,133],"signals","lead","lead signals","how","find","ready","how to","qualify","people","enrich","changes","funding"]