[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F3FSCHVGF4ZKFJV5WFF2PW":3,"skill-same:01M6F3FSCHVGF4ZKFJV5WFF2PW":74},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":31,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":73},"01M6F3FSCHVGF4ZKFJV5WFF2PW","artifact-yylo",null,"Capture and retrieve durable YYLO Ledger artifact Records with intentional profiles, payload modes, provenance, retention, and secret-safe immutable evidence.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"MIT","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-artifact-yylo\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"artifact yylo","artifact","record","modes","with provenance","inspect","true","profiles","with","retention","records","project","cli","main","community","evidence","never","find","project-management","immutable","provenance","license","dev","github","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\nThis storage convention applies only when the user\u002Fproject has adopted YYLO Ledger. Repository instructions and the requested deliverable location take precedence; a generic artifact request does not authorize moving existing plans\u002Fdocs into Ledger. Secret detection is defense in depth, not a guarantee: inspect and redact payloads before capture, including externally referenced bytes.\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\nThis storage convention applies only when the user\u002Fproject has adopted YYLO Ledger. Repository instructions and the requested deliverable location take precedence; a generic artifact request does not authorize moving existing plans\u002Fdocs into Ledger. Secret detection is defense in depth, not a guarantee: inspect and redact payloads before capture, including externally referenced bytes.\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":47,"source":48,"license":14,"category":36,"date_added":49,"description":7,"source_repo":50,"source_type":32,"argument-hint":51,"compatibility":52,"license_source":53,"enable-shell-directives":54},"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,"7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-artifact-yylo",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-11 14:20:43",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":54},[63,66,69],{"tool":64,"command":65},"npx","npx skills add boisenoise\u002Fskills-collections --skill artifact-yylo",{"tool":67,"command":68},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill artifact-yylo",{"tool":70,"command":71},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill artifact-yylo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-artifact-yylo\u002FSKILL.md",[],[75,105,129,154,173,196],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":42},"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",[],[84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"web","access","web access","official","development","browser","search","data","Tools","read","fetch","only","youtube","free tools","platform","critical","free","cover","normal","when","2026",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":117,"publishedAt":42},"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",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[107,118,30,41,87,88,39,92,119,120,121,122,123,124,125,99,126,26,127,128,104],"MCP","Budget","credentials","team","catalog","use","call","discover","external tools","scoped","blob",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":133,"sourceHtmlUrl":134,"categories":135,"keywords":141,"publishedAt":42},"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",[136],{"categoryNo":137,"categoryName":138,"taxonomyType":139,"taxonomyTypeDesc":140},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[131,41,87,39,142,143,144,145,33,146,99,147,148,149,26,150,151,152,153,128,107,104],"https","email","enrichment","business","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":158,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":42},"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",[],[162,163,164,41,87,39,165,166,142,167,119,168,169,170,33,99,171,172,128,107,104],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":177,"sourceHtmlUrl":178,"categories":179,"keywords":180,"publishedAt":42},"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",[],[181,182,41,183,87,184,39,185,186,187,188,189,99,190,191,192,193,194,195,128],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":200,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":42},"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",[],[204,205,206,41,87,39,207,35,145,208,209,99,210,211,212,213,214,215,216,128],"signals","lead","lead signals","how","ready","as","how to","qualify","people","information","enrich","changes","funding"]