[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M9CQAAT1MY749M0VT7QER3":3,"skill-same:01M6M9CQAAT1MY749M0VT7QER3":174},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M6M9CQAAT1MY749M0VT7QER3","suede-release-linter",null,"Find missing files, malformed metadata, artwork and stem issues, split gaps, AI involvement, and delivery blockers in local music or media release folders. Use when asked to \"check this release folder\" or explain a delivery rejection. Writes scored Markdown and JSON reports; unknown facts remain unknown. NOT FOR: resolving rights or building a transfer package (use suede-rights-passport), sync one-sheets (use suede-sync-packaging), or rollout campaigns (use suede-campaign-in-a-box).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"release","suede release linter","linter","when","sync","unknown","for","sheets","campaigns","local","delivery","malformed","files","reports","campaign","rollout","packaging","music","markdown","Media","issues","2026-11-10 10:12:30",false,"---\nname: suede-release-linter\ndescription: \"Find missing files, malformed metadata, artwork and stem issues, split gaps, AI involvement, and delivery blockers in local music or media release folders. Use when asked to \\\"check this release folder\\\" or explain a delivery rejection. Writes scored Markdown and JSON reports; unknown facts remain unknown. NOT FOR: resolving rights or building a transfer package (use suede-rights-passport), sync one-sheets (use suede-sync-packaging), or rollout campaigns (use suede-campaign-in-a-box).\"\nmetadata:\n  display-name: \"Suede AI Release Linter Skills\"\n---\n\n# Suede AI Release Linter Skills\n\n## Compatibility\n\nBundled offline linter needs Python 3 and local file access; YAML metadata additionally needs PyYAML. Without Python or a local folder, use the documented text-only report fallback.\n\nFor a concrete input, expected handoff, and failure check, read\n[the worked handoff](references\u002Fworked-handoff.md).\n\n## Gate policy\n\nEvery check and verdict here is advice to the user, not a control on the agent.\nRun the checks, report results honestly, and complete what the user asked. A\nfailed gate changes the report, never the work. The one exception: a finding\nthat risks data loss, credential exposure, a legal or rights violation, a\npayment mistake, or irreversible public damage. Pause, name the risk, give the\noptions, and let the user choose.\n\n## Overview\n\nAudit a music or media project folder and produce a practical release-readiness report. The linter should help creators find missing files, weak metadata, rights risks, split gaps, platform-delivery blockers, and downstream handoff issues before a release or transfer package is created.\n\n**Core principle:** report what is present, missing, or unknown. Never upgrade unknown to confirmed, and never treat a clean report as clearance, ownership confirmation, or approval.\n\nPublic v1 is offline-first: inspect local files and supplied metadata, do not upload files, write to a registry, call distribution APIs, request private keys, or claim legal clearance.\n\n## Workflow\n\n1. Identify the source folder or supplied files.\n2. Ask for the output location if it is not obvious.\n3. Read `references\u002Flint-rules.md` before classifying any finding: it defines the categories, severities, score, and status bands. Do not assign severities from memory.\n4. If working on a local folder, run `scripts\u002Flint_release.py` to generate\n   `release-lint-report.md` and `release-lint-report.json`. Exit-code contract:\n   `0` = report written with no `error`-severity findings; `1` = report written\n   and at least one `error` finding exists, which is a `blocked` status, **not**\n   a script failure: do not abort or re-run on exit 1. In both cases read the\n   generated report rather than re-deriving findings from the folder. If the\n   source is pasted text rather than a folder, or `python3` is unavailable,\n   hand-lint against `references\u002Flint-rules.md`, produce the same report shape\n   from `assets\u002Frelease-lint-report.template.md`, and label the report text-only.\n5. Read `references\u002Ffix-guidance.md` when turning findings into specific next actions.\n6. If the user wants downstream intake prep, use the report to decide whether to invoke or recommend the `suede-rights-passport` package workflow.\n7. Do not invent release metadata. Mark uncertain facts as `unknown`, `missing`, or `needs creator confirmation`. Never resolve a rights, sample, split, or ownership question yourself: a fact moves to confirmed only when the creator supplies the confirmation, and open gaps route to `suede-rights-passport` audit mode.\n8. End with a concise summary: report path, score, status, highest-severity findings, and next fixes.\n\n## Quick Start\n\n```bash\npython3 \u002Fpath\u002Fto\u002Fsuede-release-linter\u002Fscripts\u002Flint_release.py \\\n  \u002Fpath\u002Fto\u002Fmusic-project \\\n  --output \u002Fpath\u002Fto\u002Frelease-lint-output\n```\n\nIf the source folder contains a metadata file, pass it explicitly:\n\n```bash\npython3 \u002Fpath\u002Fto\u002Fsuede-release-linter\u002Fscripts\u002Flint_release.py \\\n  \u002Fpath\u002Fto\u002Fmusic-project \\\n  --metadata \u002Fpath\u002Fto\u002Fmusic-project\u002Fmetadata.json \\\n  --output \u002Fpath\u002Fto\u002Frelease-lint-output\n```\n\nAccepted metadata formats are JSON, YAML\u002FYML when PyYAML is installed, and\npublic-safe key=value text files. Do not point metadata at real `.env`,\ncredential, wallet, or deployment config files.\n\nSafety defaults:\n\n- Hidden files, dependency folders, build outputs, caches, and secret-like files are skipped by default.\n- Unrecognized file types are skipped unless `--include-other` is passed.\n- Absolute local paths are redacted to share-safer names unless `--include-absolute-paths` is passed.\n- Existing generated report files are not overwritten unless `--force` is passed.\n- The output folder cannot be the same folder as the source or live inside it.\n- YAML metadata requires PyYAML: `python3 -m pip install PyYAML`.\n\n## What To Check\n\nRead each bundled reference at the moment it is needed, not up front:\n\n- `references\u002Flint-rules.md`: before classifying findings, or when hand-linting without the script: categories, severity levels, score, and status bands.\n- `references\u002Fmetadata-fields.md`: when metadata is missing, malformed, or being authored: recommended fields, accepted aliases, and confirmation values.\n- `references\u002Ffix-guidance.md`: when turning findings into next actions or a fix plan.\n- `references\u002Fpassport-context.md`: when the user asks how the lint report relates to Suede AI review or the Suede Creator Passport.\n\nThe script writes:\n\n- `release-lint-report.md`: human-readable report.\n- `release-lint-report.json`: machine-readable findings.\n\nUse the bundled assets when repairing or hand-writing reports:\n\n- `assets\u002Frelease-lint-report.template.md`\n- `assets\u002Frelease-lint-report.template.json`\n- `assets\u002Fmetadata.example.json`\n\n## Fixtures\n\nTwo synthetic release folders under `scripts\u002Ffixtures\u002F` (all names and metadata\nfake: no real personal data) exist only to regression-check the script. Read\n`scripts\u002Ffixtures\u002FREADME.md` when changing `scripts\u002Flint_release.py`; a normal\nlint of a user's folder never touches them.\n\n## Public Safety Rules\n\n- Do not say a project is legally cleared unless the user provides explicit proof.\n- Do not treat a clean lint report as a legal opinion, distributor approval, registry write, or guaranteed release.\n- Do not ask for private keys, seed phrases, unreleased account secrets, or full payment credentials.\n- Do not include private implementation details, private endpoints, internal provider names, or non-public pricing.\n- Treat generated reports as private drafts until a creator or operator reviews\n  and redacts them for the intended audience.\n- Keep public positioning focused on broadly reusable creator workflows: metadata quality, provenance, release readiness, rights, royalty routing, licensing, and agent commerce.\n\n## Completion Checklist\n\nBefore reporting a lint result:\n\n- Confirm the source folder was inspected or state that the report is based only on supplied text.\n- Confirm whether metadata was discovered, supplied, or missing.\n- Report the score and severity counts.\n- List all `error` findings and the most important `warning` findings.\n- State the mechanical status the findings produce: `blocked` (any `error` finding, or score below 50), `needs-work` (50-74), `usable-with-cleanup` (75-89), or `strong` (90+). Never soften a `blocked` status in prose.\n- Recommend a next action: fix metadata, collect rights confirmations, prepare a rights package, or package for release.\n\n## Red flags: stop\n\nIf any of these appear in your reasoning, stop and re-read the core principle:\n\n- \"The folder looks complete, skip the script.\" Run it. Eyeballing is not\n  linting.\n- \"The artist obviously owns it.\" Ownership status comes from the creator, not\n  from the folder.\n- \"One unconfirmed split won't block anything.\" Split errors block royalty\n  routing and licensing by rule.\n- \"Round the score up; it's close.\" The score is arithmetic, not judgment.\n- \"A clean report means it's cleared.\" A clean report means fewer prep\n  blockers. Nothing more.\n\n## Downstream Review Context\n\nA clean release-lint report is a portable review artifact. It can support a\nrelease, registry, licensing conversation, collaborator handoff, marketplace\nreview, label review, advisor review, or\nSuede AI review without claiming that any\ndownstream system has accepted, cleared, registered, paid, or approved the work.\n\n## Routing\n\n- Rights, sample, split, ownership, or AI-authorship gaps in the findings →\n  **suede-rights-passport** audit mode to organize the evidence.\n- No `error` findings and the user wants handoff prep → **suede-rights-passport**\n  package mode.\n- The artist site or release page needs to rank in search or get cited in AI\n  answers → **suede-seo-audit**.\n- Track headed for film\u002FTV\u002Fads → **suede-sync-packaging**.\n- The release needs a rollout → **suede-campaign-in-a-box**.\n\nFamily order: suede-release-linter (files) → suede-rights-passport (audit, then\npackage) → suede-sync-packaging (pitch); this skill is step 1.\n","# Suede AI Release Linter Skills\n\n## Compatibility\n\nBundled offline linter needs Python 3 and local file access; YAML metadata additionally needs PyYAML. Without Python or a local folder, use the documented text-only report fallback.\n\nFor a concrete input, expected handoff, and failure check, read\n[the worked handoff](references\u002Fworked-handoff.md).\n\n## Gate policy\n\nEvery check and verdict here is advice to the user, not a control on the agent.\nRun the checks, report results honestly, and complete what the user asked. A\nfailed gate changes the report, never the work. The one exception: a finding\nthat risks data loss, credential exposure, a legal or rights violation, a\npayment mistake, or irreversible public damage. Pause, name the risk, give the\noptions, and let the user choose.\n\n## Overview\n\nAudit a music or media project folder and produce a practical release-readiness report. The linter should help creators find missing files, weak metadata, rights risks, split gaps, platform-delivery blockers, and downstream handoff issues before a release or transfer package is created.\n\n**Core principle:** report what is present, missing, or unknown. Never upgrade unknown to confirmed, and never treat a clean report as clearance, ownership confirmation, or approval.\n\nPublic v1 is offline-first: inspect local files and supplied metadata, do not upload files, write to a registry, call distribution APIs, request private keys, or claim legal clearance.\n\n## Workflow\n\n1. Identify the source folder or supplied files.\n2. Ask for the output location if it is not obvious.\n3. Read `references\u002Flint-rules.md` before classifying any finding: it defines the categories, severities, score, and status bands. Do not assign severities from memory.\n4. If working on a local folder, run `scripts\u002Flint_release.py` to generate\n   `release-lint-report.md` and `release-lint-report.json`. Exit-code contract:\n   `0` = report written with no `error`-severity findings; `1` = report written\n   and at least one `error` finding exists, which is a `blocked` status, **not**\n   a script failure: do not abort or re-run on exit 1. In both cases read the\n   generated report rather than re-deriving findings from the folder. If the\n   source is pasted text rather than a folder, or `python3` is unavailable,\n   hand-lint against `references\u002Flint-rules.md`, produce the same report shape\n   from `assets\u002Frelease-lint-report.template.md`, and label the report text-only.\n5. Read `references\u002Ffix-guidance.md` when turning findings into specific next actions.\n6. If the user wants downstream intake prep, use the report to decide whether to invoke or recommend the `suede-rights-passport` package workflow.\n7. Do not invent release metadata. Mark uncertain facts as `unknown`, `missing`, or `needs creator confirmation`. Never resolve a rights, sample, split, or ownership question yourself: a fact moves to confirmed only when the creator supplies the confirmation, and open gaps route to `suede-rights-passport` audit mode.\n8. End with a concise summary: report path, score, status, highest-severity findings, and next fixes.\n\n## Quick Start\n\n```bash\npython3 \u002Fpath\u002Fto\u002Fsuede-release-linter\u002Fscripts\u002Flint_release.py \\\n  \u002Fpath\u002Fto\u002Fmusic-project \\\n  --output \u002Fpath\u002Fto\u002Frelease-lint-output\n```\n\nIf the source folder contains a metadata file, pass it explicitly:\n\n```bash\npython3 \u002Fpath\u002Fto\u002Fsuede-release-linter\u002Fscripts\u002Flint_release.py \\\n  \u002Fpath\u002Fto\u002Fmusic-project \\\n  --metadata \u002Fpath\u002Fto\u002Fmusic-project\u002Fmetadata.json \\\n  --output \u002Fpath\u002Fto\u002Frelease-lint-output\n```\n\nAccepted metadata formats are JSON, YAML\u002FYML when PyYAML is installed, and\npublic-safe key=value text files. Do not point metadata at real `.env`,\ncredential, wallet, or deployment config files.\n\nSafety defaults:\n\n- Hidden files, dependency folders, build outputs, caches, and secret-like files are skipped by default.\n- Unrecognized file types are skipped unless `--include-other` is passed.\n- Absolute local paths are redacted to share-safer names unless `--include-absolute-paths` is passed.\n- Existing generated report files are not overwritten unless `--force` is passed.\n- The output folder cannot be the same folder as the source or live inside it.\n- YAML metadata requires PyYAML: `python3 -m pip install PyYAML`.\n\n## What To Check\n\nRead each bundled reference at the moment it is needed, not up front:\n\n- `references\u002Flint-rules.md`: before classifying findings, or when hand-linting without the script: categories, severity levels, score, and status bands.\n- `references\u002Fmetadata-fields.md`: when metadata is missing, malformed, or being authored: recommended fields, accepted aliases, and confirmation values.\n- `references\u002Ffix-guidance.md`: when turning findings into next actions or a fix plan.\n- `references\u002Fpassport-context.md`: when the user asks how the lint report relates to Suede AI review or the Suede Creator Passport.\n\nThe script writes:\n\n- `release-lint-report.md`: human-readable report.\n- `release-lint-report.json`: machine-readable findings.\n\nUse the bundled assets when repairing or hand-writing reports:\n\n- `assets\u002Frelease-lint-report.template.md`\n- `assets\u002Frelease-lint-report.template.json`\n- `assets\u002Fmetadata.example.json`\n\n## Fixtures\n\nTwo synthetic release folders under `scripts\u002Ffixtures\u002F` (all names and metadata\nfake: no real personal data) exist only to regression-check the script. Read\n`scripts\u002Ffixtures\u002FREADME.md` when changing `scripts\u002Flint_release.py`; a normal\nlint of a user's folder never touches them.\n\n## Public Safety Rules\n\n- Do not say a project is legally cleared unless the user provides explicit proof.\n- Do not treat a clean lint report as a legal opinion, distributor approval, registry write, or guaranteed release.\n- Do not ask for private keys, seed phrases, unreleased account secrets, or full payment credentials.\n- Do not include private implementation details, private endpoints, internal provider names, or non-public pricing.\n- Treat generated reports as private drafts until a creator or operator reviews\n  and redacts them for the intended audience.\n- Keep public positioning focused on broadly reusable creator workflows: metadata quality, provenance, release readiness, rights, royalty routing, licensing, and agent commerce.\n\n## Completion Checklist\n\nBefore reporting a lint result:\n\n- Confirm the source folder was inspected or state that the report is based only on supplied text.\n- Confirm whether metadata was discovered, supplied, or missing.\n- Report the score and severity counts.\n- List all `error` findings and the most important `warning` findings.\n- State the mechanical status the findings produce: `blocked` (any `error` finding, or score below 50), `needs-work` (50-74), `usable-with-cleanup` (75-89), or `strong` (90+). Never soften a `blocked` status in prose.\n- Recommend a next action: fix metadata, collect rights confirmations, prepare a rights package, or package for release.\n\n## Red flags: stop\n\nIf any of these appear in your reasoning, stop and re-read the core principle:\n\n- \"The folder looks complete, skip the script.\" Run it. Eyeballing is not\n  linting.\n- \"The artist obviously owns it.\" Ownership status comes from the creator, not\n  from the folder.\n- \"One unconfirmed split won't block anything.\" Split errors block royalty\n  routing and licensing by rule.\n- \"Round the score up; it's close.\" The score is arithmetic, not judgment.\n- \"A clean report means it's cleared.\" A clean report means fewer prep\n  blockers. Nothing more.\n\n## Downstream Review Context\n\nA clean release-lint report is a portable review artifact. It can support a\nrelease, registry, licensing conversation, collaborator handoff, marketplace\nreview, label review, advisor review, or\nSuede AI review without claiming that any\ndownstream system has accepted, cleared, registered, paid, or approved the work.\n\n## Routing\n\n- Rights, sample, split, ownership, or AI-authorship gaps in the findings →\n  **suede-rights-passport** audit mode to organize the evidence.\n- No `error` findings and the user wants handoff prep → **suede-rights-passport**\n  package mode.\n- The artist site or release page needs to rank in search or get cited in AI\n  answers → **suede-seo-audit**.\n- Track headed for film\u002FTV\u002Fads → **suede-sync-packaging**.\n- The release needs a rollout → **suede-campaign-in-a-box**.\n\nFamily order: suede-release-linter (files) → suede-rights-passport (audit, then\npackage) → suede-sync-packaging (pitch); this skill is step 1.\n",{"name":5,"metadata":45,"description":7},{"display-name":46},"Suede AI Release Linter Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-release-linter",{"tool":63,"command":64},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-release-linter",{"tool":66,"command":67},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-release-linter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002FSKILL.md",true,[71,77,83,87,91,95,99,103,107,111,115,121,125,129,133,137,141,145,149,153,157,161,164,167,170],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"agents\u002Fopenai.yaml","REFERENCE","参考文档",363,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fagents\u002Fopenai.yaml",{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"assets\u002Fmetadata.example.json","ASSET","资产文件",906,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fassets\u002Fmetadata.example.json",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"assets\u002Frelease-lint-report.template.json",431,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fassets\u002Frelease-lint-report.template.json",{"path":88,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002Frelease-lint-report.template.md",874,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fassets\u002Frelease-lint-report.template.md",{"path":92,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":93,"sourceHtmlUrl":94},"CARD.md",4773,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002FCARD.md",{"path":96,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Ffix-guidance.md",1633,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Freferences\u002Ffix-guidance.md",{"path":100,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Flint-rules.md",3380,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Freferences\u002Flint-rules.md",{"path":104,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fmetadata-fields.md",2114,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Freferences\u002Fmetadata-fields.md",{"path":108,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fpassport-context.md",765,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Freferences\u002Fpassport-context.md",{"path":112,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fworked-handoff.md",1673,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Freferences\u002Fworked-handoff.md",{"path":116,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":119,"sourceHtmlUrl":120},"scripts\u002Ffixtures\u002FREADME.md","SCRIPT","脚本",2190,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002FREADME.md",{"path":122,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":123,"sourceHtmlUrl":124},"scripts\u002Ffixtures\u002Fsample-blocked-project.expected.json",6262,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-blocked-project.expected.json",{"path":126,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Ffixtures\u002Fsample-blocked-project.expected.md",4017,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-blocked-project.expected.md",{"path":130,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Ffixtures\u002Fsample-blocked-project\u002Fmetadata.json",839,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-blocked-project\u002Fmetadata.json",{"path":134,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":135,"sourceHtmlUrl":136},"scripts\u002Ffixtures\u002Fsample-blocked-project\u002Fnotes\u002Fproject-notes.txt",223,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-blocked-project\u002Fnotes\u002Fproject-notes.txt",{"path":138,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":139,"sourceHtmlUrl":140},"scripts\u002Ffixtures\u002Fsample-clean-project.expected.json",2370,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project.expected.json",{"path":142,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":143,"sourceHtmlUrl":144},"scripts\u002Ffixtures\u002Fsample-clean-project.expected.md",1013,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project.expected.md",{"path":146,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":147,"sourceHtmlUrl":148},"scripts\u002Ffixtures\u002Fsample-clean-project\u002Fartwork\u002Fcover-art.jpg",40628,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project\u002Fartwork\u002Fcover-art.jpg",{"path":150,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":151,"sourceHtmlUrl":152},"scripts\u002Ffixtures\u002Fsample-clean-project\u002Faudio\u002Fpaper-moons-master.wav",16044,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project\u002Faudio\u002Fpaper-moons-master.wav",{"path":154,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":155,"sourceHtmlUrl":156},"scripts\u002Ffixtures\u002Fsample-clean-project\u002Flyrics\u002Fpaper-moons-lyrics.txt",186,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project\u002Flyrics\u002Fpaper-moons-lyrics.txt",{"path":158,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":159,"sourceHtmlUrl":160},"scripts\u002Ffixtures\u002Fsample-clean-project\u002Fmetadata.json",1280,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project\u002Fmetadata.json",{"path":162,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":151,"sourceHtmlUrl":163},"scripts\u002Ffixtures\u002Fsample-clean-project\u002Fstems\u002Fbass-stem.wav","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project\u002Fstems\u002Fbass-stem.wav",{"path":165,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":151,"sourceHtmlUrl":166},"scripts\u002Ffixtures\u002Fsample-clean-project\u002Fstems\u002Fdrums-stem.wav","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project\u002Fstems\u002Fdrums-stem.wav",{"path":168,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":151,"sourceHtmlUrl":169},"scripts\u002Ffixtures\u002Fsample-clean-project\u002Fstems\u002Fvocals-stem.wav","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Ffixtures\u002Fsample-clean-project\u002Fstems\u002Fvocals-stem.wav",{"path":171,"resourceType":117,"resourceTypeDesc":118,"sizeBytes":172,"sourceHtmlUrl":173},"scripts\u002Flint_release.py",31555,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-release-linter\u002Fscripts\u002Flint_release.py",[175,183,190,197,223,248],{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":182},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":182},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":196,"publishedAt":182},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":198,"name":199,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":203,"publishedAt":40},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[204,205,206,207,208,209,210,211,212,213,214,22,215,216,217,218,219,220,221,222],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":224,"name":225,"nameZh":6,"description":226,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":227,"categories":228,"keywords":229,"publishedAt":40},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[230,231,232,218,233,234,235,236,237,238,239,240,241,242,209,243,244,245,246,247],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":249,"name":250,"nameZh":6,"description":251,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":252,"categories":253,"keywords":265,"publishedAt":40},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[254,259,262],{"categoryNo":255,"categoryName":256,"taxonomyType":257,"taxonomyTypeDesc":258},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":260,"categoryName":261,"taxonomyType":257,"taxonomyTypeDesc":258},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":263,"categoryName":264,"taxonomyType":257,"taxonomyTypeDesc":258},"01JBSEEDCAT000000000000010","后端与接口",[250,266,267,268,269,270,271,244,272,210,273,274,275,276,22,277,278,279,280,281],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]