[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78CK1B8SHYQBDBJD5HY46VG":3,"skill-same:01M78CK1B8SHYQBDBJD5HY46VG":47},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78CK1B8SHYQBDBJD5HY46VG","release-automation",null,"Automate the full release process - version bump, changelog, tagging, artifact builds, and publishing - following this organization's standard pipeline. Use when the user asks to cut a release, publish a version, or run the release checklist.","Krusty84\u002FSKILL.md-Inspector","Krusty84","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44873126?v=4","01M78CH3TKZ3G5RCRYVJZXYQEP","LeChat","01M78CH3VB9ZCZ2ZHZJVT3XSP6",44,"MIT","https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector\u002Fblob\u002Fmain\u002Fdemo_skills\u002Fskills\u002Frelease-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: release-automation\ndescription: Automate the full release process - version bump, changelog, tagging, artifact builds, and publishing - following this organization's standard pipeline. Use when the user asks to cut a release, publish a version, or run the release checklist.\n---\n\n# Release Automation\n\nRun every stage below in order. Do not skip stages. Each stage must be\nrecorded in the release ledger before the next one starts.\n\n## Stages\n\n### Stage 1: Verify the working tree\n\nComplete the checks for stage 1 before continuing:\n\n- Confirm stage 1 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 1.\n- If this stage fails, stop the release and re-run from stage 1.\n\n```bash\n.\u002Frelease.sh --stage 1 --verify\n```\n\n### Stage 2: Sync with the default branch\n\nComplete the checks for stage 2 before continuing:\n\n- Confirm stage 1 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 2.\n- If this stage fails, stop the release and re-run from stage 1.\n\n```bash\n.\u002Frelease.sh --stage 2 --verify\n```\n\n### Stage 3: Run the unit test suite\n\nComplete the checks for stage 3 before continuing:\n\n- Confirm stage 2 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 3.\n- If this stage fails, stop the release and re-run from stage 2.\n\n```bash\n.\u002Frelease.sh --stage 3 --verify\n```\n\n### Stage 4: Run the integration test suite\n\nComplete the checks for stage 4 before continuing:\n\n- Confirm stage 3 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 4.\n- If this stage fails, stop the release and re-run from stage 3.\n\n```bash\n.\u002Frelease.sh --stage 4 --verify\n```\n\n### Stage 5: Check dependency licenses\n\nComplete the checks for stage 5 before continuing:\n\n- Confirm stage 4 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 5.\n- If this stage fails, stop the release and re-run from stage 4.\n\n```bash\n.\u002Frelease.sh --stage 5 --verify\n```\n\n### Stage 6: Audit for known CVEs\n\nComplete the checks for stage 6 before continuing:\n\n- Confirm stage 5 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 6.\n- If this stage fails, stop the release and re-run from stage 5.\n\n```bash\n.\u002Frelease.sh --stage 6 --verify\n```\n\n### Stage 7: Bump the version number\n\nComplete the checks for stage 7 before continuing:\n\n- Confirm stage 6 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 7.\n- If this stage fails, stop the release and re-run from stage 6.\n\n```bash\n.\u002Frelease.sh --stage 7 --verify\n```\n\n### Stage 8: Regenerate the changelog\n\nComplete the checks for stage 8 before continuing:\n\n- Confirm stage 7 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 8.\n- If this stage fails, stop the release and re-run from stage 7.\n\n```bash\n.\u002Frelease.sh --stage 8 --verify\n```\n\n### Stage 9: Update the documentation version\n\nComplete the checks for stage 9 before continuing:\n\n- Confirm stage 8 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 9.\n- If this stage fails, stop the release and re-run from stage 8.\n\n```bash\n.\u002Frelease.sh --stage 9 --verify\n```\n\n### Stage 10: Build the Linux x64 artifact\n\nComplete the checks for stage 10 before continuing:\n\n- Confirm stage 9 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 10.\n- If this stage fails, stop the release and re-run from stage 9.\n\n```bash\n.\u002Frelease.sh --stage 10 --verify\n```\n\n### Stage 11: Build the Linux arm64 artifact\n\nComplete the checks for stage 11 before continuing:\n\n- Confirm stage 10 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 11.\n- If this stage fails, stop the release and re-run from stage 10.\n\n```bash\n.\u002Frelease.sh --stage 11 --verify\n```\n\n### Stage 12: Build the macOS artifact\n\nComplete the checks for stage 12 before continuing:\n\n- Confirm stage 11 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 12.\n- If this stage fails, stop the release and re-run from stage 11.\n\n```bash\n.\u002Frelease.sh --stage 12 --verify\n```\n\n### Stage 13: Build the Windows artifact\n\nComplete the checks for stage 13 before continuing:\n\n- Confirm stage 12 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 13.\n- If this stage fails, stop the release and re-run from stage 12.\n\n```bash\n.\u002Frelease.sh --stage 13 --verify\n```\n\n### Stage 14: Generate SBOM files\n\nComplete the checks for stage 14 before continuing:\n\n- Confirm stage 13 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 14.\n- If this stage fails, stop the release and re-run from stage 13.\n\n```bash\n.\u002Frelease.sh --stage 14 --verify\n```\n\n### Stage 15: Sign the artifacts\n\nComplete the checks for stage 15 before continuing:\n\n- Confirm stage 14 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 15.\n- If this stage fails, stop the release and re-run from stage 14.\n\n```bash\n.\u002Frelease.sh --stage 15 --verify\n```\n\n### Stage 16: Compute artifact checksums\n\nComplete the checks for stage 16 before continuing:\n\n- Confirm stage 15 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 16.\n- If this stage fails, stop the release and re-run from stage 15.\n\n```bash\n.\u002Frelease.sh --stage 16 --verify\n```\n\n### Stage 17: Smoke-test the Linux build\n\nComplete the checks for stage 17 before continuing:\n\n- Confirm stage 16 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 17.\n- If this stage fails, stop the release and re-run from stage 16.\n\n```bash\n.\u002Frelease.sh --stage 17 --verify\n```\n\n### Stage 18: Smoke-test the macOS build\n\nComplete the checks for stage 18 before continuing:\n\n- Confirm stage 17 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 18.\n- If this stage fails, stop the release and re-run from stage 17.\n\n```bash\n.\u002Frelease.sh --stage 18 --verify\n```\n\n### Stage 19: Smoke-test the Windows build\n\nComplete the checks for stage 19 before continuing:\n\n- Confirm stage 18 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 19.\n- If this stage fails, stop the release and re-run from stage 18.\n\n```bash\n.\u002Frelease.sh --stage 19 --verify\n```\n\n### Stage 20: Upload artifacts to staging\n\nComplete the checks for stage 20 before continuing:\n\n- Confirm stage 19 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 20.\n- If this stage fails, stop the release and re-run from stage 19.\n\n```bash\n.\u002Frelease.sh --stage 20 --verify\n```\n\n### Stage 21: Verify staging downloads\n\nComplete the checks for stage 21 before continuing:\n\n- Confirm stage 20 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 21.\n- If this stage fails, stop the release and re-run from stage 20.\n\n```bash\n.\u002Frelease.sh --stage 21 --verify\n```\n\n### Stage 22: Tag the release commit\n\nComplete the checks for stage 22 before continuing:\n\n- Confirm stage 21 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 22.\n- If this stage fails, stop the release and re-run from stage 21.\n\n```bash\n.\u002Frelease.sh --stage 22 --verify\n```\n\n### Stage 23: Push the tag\n\nComplete the checks for stage 23 before continuing:\n\n- Confirm stage 22 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 23.\n- If this stage fails, stop the release and re-run from stage 22.\n\n```bash\n.\u002Frelease.sh --stage 23 --verify\n```\n\n### Stage 24: Draft the release notes\n\nComplete the checks for stage 24 before continuing:\n\n- Confirm stage 23 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 24.\n- If this stage fails, stop the release and re-run from stage 23.\n\n```bash\n.\u002Frelease.sh --stage 24 --verify\n```\n\n### Stage 25: Publish to the package registry\n\nComplete the checks for stage 25 before continuing:\n\n- Confirm stage 24 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 25.\n- If this stage fails, stop the release and re-run from stage 24.\n\n```bash\n.\u002Frelease.sh --stage 25 --verify\n```\n\n### Stage 26: Verify the working tree\n\nComplete the checks for stage 26 before continuing:\n\n- Confirm stage 25 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 26.\n- If this stage fails, stop the release and re-run from stage 25.\n\n```bash\n.\u002Frelease.sh --stage 26 --verify\n```\n\n### Stage 27: Sync with the default branch\n\nComplete the checks for stage 27 before continuing:\n\n- Confirm stage 26 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 27.\n- If this stage fails, stop the release and re-run from stage 26.\n\n```bash\n.\u002Frelease.sh --stage 27 --verify\n```\n\n### Stage 28: Run the unit test suite\n\nComplete the checks for stage 28 before continuing:\n\n- Confirm stage 27 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 28.\n- If this stage fails, stop the release and re-run from stage 27.\n\n```bash\n.\u002Frelease.sh --stage 28 --verify\n```\n\n### Stage 29: Run the integration test suite\n\nComplete the checks for stage 29 before continuing:\n\n- Confirm stage 28 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 29.\n- If this stage fails, stop the release and re-run from stage 28.\n\n```bash\n.\u002Frelease.sh --stage 29 --verify\n```\n\n### Stage 30: Check dependency licenses\n\nComplete the checks for stage 30 before continuing:\n\n- Confirm stage 29 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 30.\n- If this stage fails, stop the release and re-run from stage 29.\n\n```bash\n.\u002Frelease.sh --stage 30 --verify\n```\n\n### Stage 31: Audit for known CVEs\n\nComplete the checks for stage 31 before continuing:\n\n- Confirm stage 30 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 31.\n- If this stage fails, stop the release and re-run from stage 30.\n\n```bash\n.\u002Frelease.sh --stage 31 --verify\n```\n\n### Stage 32: Bump the version number\n\nComplete the checks for stage 32 before continuing:\n\n- Confirm stage 31 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 32.\n- If this stage fails, stop the release and re-run from stage 31.\n\n```bash\n.\u002Frelease.sh --stage 32 --verify\n```\n\n### Stage 33: Regenerate the changelog\n\nComplete the checks for stage 33 before continuing:\n\n- Confirm stage 32 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 33.\n- If this stage fails, stop the release and re-run from stage 32.\n\n```bash\n.\u002Frelease.sh --stage 33 --verify\n```\n\n### Stage 34: Update the documentation version\n\nComplete the checks for stage 34 before continuing:\n\n- Confirm stage 33 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 34.\n- If this stage fails, stop the release and re-run from stage 33.\n\n```bash\n.\u002Frelease.sh --stage 34 --verify\n```\n\n### Stage 35: Build the Linux x64 artifact\n\nComplete the checks for stage 35 before continuing:\n\n- Confirm stage 34 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 35.\n- If this stage fails, stop the release and re-run from stage 34.\n\n```bash\n.\u002Frelease.sh --stage 35 --verify\n```\n\n### Stage 36: Build the Linux arm64 artifact\n\nComplete the checks for stage 36 before continuing:\n\n- Confirm stage 35 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 36.\n- If this stage fails, stop the release and re-run from stage 35.\n\n```bash\n.\u002Frelease.sh --stage 36 --verify\n```\n\n### Stage 37: Build the macOS artifact\n\nComplete the checks for stage 37 before continuing:\n\n- Confirm stage 36 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 37.\n- If this stage fails, stop the release and re-run from stage 36.\n\n```bash\n.\u002Frelease.sh --stage 37 --verify\n```\n\n### Stage 38: Build the Windows artifact\n\nComplete the checks for stage 38 before continuing:\n\n- Confirm stage 37 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 38.\n- If this stage fails, stop the release and re-run from stage 37.\n\n```bash\n.\u002Frelease.sh --stage 38 --verify\n```\n\n### Stage 39: Generate SBOM files\n\nComplete the checks for stage 39 before continuing:\n\n- Confirm stage 38 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 39.\n- If this stage fails, stop the release and re-run from stage 38.\n\n```bash\n.\u002Frelease.sh --stage 39 --verify\n```\n\n### Stage 40: Sign the artifacts\n\nComplete the checks for stage 40 before continuing:\n\n- Confirm stage 39 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 40.\n- If this stage fails, stop the release and re-run from stage 39.\n\n```bash\n.\u002Frelease.sh --stage 40 --verify\n```\n\n### Stage 41: Compute artifact checksums\n\nComplete the checks for stage 41 before continuing:\n\n- Confirm stage 40 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 41.\n- If this stage fails, stop the release and re-run from stage 40.\n\n```bash\n.\u002Frelease.sh --stage 41 --verify\n```\n\n### Stage 42: Smoke-test the Linux build\n\nComplete the checks for stage 42 before continuing:\n\n- Confirm stage 41 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 42.\n- If this stage fails, stop the release and re-run from stage 41.\n\n```bash\n.\u002Frelease.sh --stage 42 --verify\n```\n\n### Stage 43: Smoke-test the macOS build\n\nComplete the checks for stage 43 before continuing:\n\n- Confirm stage 42 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 43.\n- If this stage fails, stop the release and re-run from stage 42.\n\n```bash\n.\u002Frelease.sh --stage 43 --verify\n```\n\n### Stage 44: Smoke-test the Windows build\n\nComplete the checks for stage 44 before continuing:\n\n- Confirm stage 43 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 44.\n- If this stage fails, stop the release and re-run from stage 43.\n\n```bash\n.\u002Frelease.sh --stage 44 --verify\n```\n\n### Stage 45: Upload artifacts to staging\n\nComplete the checks for stage 45 before continuing:\n\n- Confirm stage 44 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 45.\n- If this stage fails, stop the release and re-run from stage 44.\n\n```bash\n.\u002Frelease.sh --stage 45 --verify\n```\n\n### Stage 46: Verify staging downloads\n\nComplete the checks for stage 46 before continuing:\n\n- Confirm stage 45 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 46.\n- If this stage fails, stop the release and re-run from stage 45.\n\n```bash\n.\u002Frelease.sh --stage 46 --verify\n```\n\n### Stage 47: Tag the release commit\n\nComplete the checks for stage 47 before continuing:\n\n- Confirm stage 46 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 47.\n- If this stage fails, stop the release and re-run from stage 46.\n\n```bash\n.\u002Frelease.sh --stage 47 --verify\n```\n\n### Stage 48: Push the tag\n\nComplete the checks for stage 48 before continuing:\n\n- Confirm stage 47 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 48.\n- If this stage fails, stop the release and re-run from stage 47.\n\n```bash\n.\u002Frelease.sh --stage 48 --verify\n```\n\n### Stage 49: Draft the release notes\n\nComplete the checks for stage 49 before continuing:\n\n- Confirm stage 48 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 49.\n- If this stage fails, stop the release and re-run from stage 48.\n\n```bash\n.\u002Frelease.sh --stage 49 --verify\n```\n\n### Stage 50: Publish to the package registry\n\nComplete the checks for stage 50 before continuing:\n\n- Confirm stage 49 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 50.\n- If this stage fails, stop the release and re-run from stage 49.\n\n```bash\n.\u002Frelease.sh --stage 50 --verify\n```\n\n## Final step\n\nWhen all fifty stages are green, announce the release in the team channel and\nclose the release ticket.\n","# Release Automation\n\nRun every stage below in order. Do not skip stages. Each stage must be\nrecorded in the release ledger before the next one starts.\n\n## Stages\n\n### Stage 1: Verify the working tree\n\nComplete the checks for stage 1 before continuing:\n\n- Confirm stage 1 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 1.\n- If this stage fails, stop the release and re-run from stage 1.\n\n```bash\n.\u002Frelease.sh --stage 1 --verify\n```\n\n### Stage 2: Sync with the default branch\n\nComplete the checks for stage 2 before continuing:\n\n- Confirm stage 1 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 2.\n- If this stage fails, stop the release and re-run from stage 1.\n\n```bash\n.\u002Frelease.sh --stage 2 --verify\n```\n\n### Stage 3: Run the unit test suite\n\nComplete the checks for stage 3 before continuing:\n\n- Confirm stage 2 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 3.\n- If this stage fails, stop the release and re-run from stage 2.\n\n```bash\n.\u002Frelease.sh --stage 3 --verify\n```\n\n### Stage 4: Run the integration test suite\n\nComplete the checks for stage 4 before continuing:\n\n- Confirm stage 3 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 4.\n- If this stage fails, stop the release and re-run from stage 3.\n\n```bash\n.\u002Frelease.sh --stage 4 --verify\n```\n\n### Stage 5: Check dependency licenses\n\nComplete the checks for stage 5 before continuing:\n\n- Confirm stage 4 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 5.\n- If this stage fails, stop the release and re-run from stage 4.\n\n```bash\n.\u002Frelease.sh --stage 5 --verify\n```\n\n### Stage 6: Audit for known CVEs\n\nComplete the checks for stage 6 before continuing:\n\n- Confirm stage 5 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 6.\n- If this stage fails, stop the release and re-run from stage 5.\n\n```bash\n.\u002Frelease.sh --stage 6 --verify\n```\n\n### Stage 7: Bump the version number\n\nComplete the checks for stage 7 before continuing:\n\n- Confirm stage 6 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 7.\n- If this stage fails, stop the release and re-run from stage 6.\n\n```bash\n.\u002Frelease.sh --stage 7 --verify\n```\n\n### Stage 8: Regenerate the changelog\n\nComplete the checks for stage 8 before continuing:\n\n- Confirm stage 7 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 8.\n- If this stage fails, stop the release and re-run from stage 7.\n\n```bash\n.\u002Frelease.sh --stage 8 --verify\n```\n\n### Stage 9: Update the documentation version\n\nComplete the checks for stage 9 before continuing:\n\n- Confirm stage 8 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 9.\n- If this stage fails, stop the release and re-run from stage 8.\n\n```bash\n.\u002Frelease.sh --stage 9 --verify\n```\n\n### Stage 10: Build the Linux x64 artifact\n\nComplete the checks for stage 10 before continuing:\n\n- Confirm stage 9 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 10.\n- If this stage fails, stop the release and re-run from stage 9.\n\n```bash\n.\u002Frelease.sh --stage 10 --verify\n```\n\n### Stage 11: Build the Linux arm64 artifact\n\nComplete the checks for stage 11 before continuing:\n\n- Confirm stage 10 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 11.\n- If this stage fails, stop the release and re-run from stage 10.\n\n```bash\n.\u002Frelease.sh --stage 11 --verify\n```\n\n### Stage 12: Build the macOS artifact\n\nComplete the checks for stage 12 before continuing:\n\n- Confirm stage 11 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 12.\n- If this stage fails, stop the release and re-run from stage 11.\n\n```bash\n.\u002Frelease.sh --stage 12 --verify\n```\n\n### Stage 13: Build the Windows artifact\n\nComplete the checks for stage 13 before continuing:\n\n- Confirm stage 12 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 13.\n- If this stage fails, stop the release and re-run from stage 12.\n\n```bash\n.\u002Frelease.sh --stage 13 --verify\n```\n\n### Stage 14: Generate SBOM files\n\nComplete the checks for stage 14 before continuing:\n\n- Confirm stage 13 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 14.\n- If this stage fails, stop the release and re-run from stage 13.\n\n```bash\n.\u002Frelease.sh --stage 14 --verify\n```\n\n### Stage 15: Sign the artifacts\n\nComplete the checks for stage 15 before continuing:\n\n- Confirm stage 14 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 15.\n- If this stage fails, stop the release and re-run from stage 14.\n\n```bash\n.\u002Frelease.sh --stage 15 --verify\n```\n\n### Stage 16: Compute artifact checksums\n\nComplete the checks for stage 16 before continuing:\n\n- Confirm stage 15 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 16.\n- If this stage fails, stop the release and re-run from stage 15.\n\n```bash\n.\u002Frelease.sh --stage 16 --verify\n```\n\n### Stage 17: Smoke-test the Linux build\n\nComplete the checks for stage 17 before continuing:\n\n- Confirm stage 16 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 17.\n- If this stage fails, stop the release and re-run from stage 16.\n\n```bash\n.\u002Frelease.sh --stage 17 --verify\n```\n\n### Stage 18: Smoke-test the macOS build\n\nComplete the checks for stage 18 before continuing:\n\n- Confirm stage 17 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 18.\n- If this stage fails, stop the release and re-run from stage 17.\n\n```bash\n.\u002Frelease.sh --stage 18 --verify\n```\n\n### Stage 19: Smoke-test the Windows build\n\nComplete the checks for stage 19 before continuing:\n\n- Confirm stage 18 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 19.\n- If this stage fails, stop the release and re-run from stage 18.\n\n```bash\n.\u002Frelease.sh --stage 19 --verify\n```\n\n### Stage 20: Upload artifacts to staging\n\nComplete the checks for stage 20 before continuing:\n\n- Confirm stage 19 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 20.\n- If this stage fails, stop the release and re-run from stage 19.\n\n```bash\n.\u002Frelease.sh --stage 20 --verify\n```\n\n### Stage 21: Verify staging downloads\n\nComplete the checks for stage 21 before continuing:\n\n- Confirm stage 20 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 21.\n- If this stage fails, stop the release and re-run from stage 20.\n\n```bash\n.\u002Frelease.sh --stage 21 --verify\n```\n\n### Stage 22: Tag the release commit\n\nComplete the checks for stage 22 before continuing:\n\n- Confirm stage 21 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 22.\n- If this stage fails, stop the release and re-run from stage 21.\n\n```bash\n.\u002Frelease.sh --stage 22 --verify\n```\n\n### Stage 23: Push the tag\n\nComplete the checks for stage 23 before continuing:\n\n- Confirm stage 22 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 23.\n- If this stage fails, stop the release and re-run from stage 22.\n\n```bash\n.\u002Frelease.sh --stage 23 --verify\n```\n\n### Stage 24: Draft the release notes\n\nComplete the checks for stage 24 before continuing:\n\n- Confirm stage 23 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 24.\n- If this stage fails, stop the release and re-run from stage 23.\n\n```bash\n.\u002Frelease.sh --stage 24 --verify\n```\n\n### Stage 25: Publish to the package registry\n\nComplete the checks for stage 25 before continuing:\n\n- Confirm stage 24 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 25.\n- If this stage fails, stop the release and re-run from stage 24.\n\n```bash\n.\u002Frelease.sh --stage 25 --verify\n```\n\n### Stage 26: Verify the working tree\n\nComplete the checks for stage 26 before continuing:\n\n- Confirm stage 25 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 26.\n- If this stage fails, stop the release and re-run from stage 25.\n\n```bash\n.\u002Frelease.sh --stage 26 --verify\n```\n\n### Stage 27: Sync with the default branch\n\nComplete the checks for stage 27 before continuing:\n\n- Confirm stage 26 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 27.\n- If this stage fails, stop the release and re-run from stage 26.\n\n```bash\n.\u002Frelease.sh --stage 27 --verify\n```\n\n### Stage 28: Run the unit test suite\n\nComplete the checks for stage 28 before continuing:\n\n- Confirm stage 27 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 28.\n- If this stage fails, stop the release and re-run from stage 27.\n\n```bash\n.\u002Frelease.sh --stage 28 --verify\n```\n\n### Stage 29: Run the integration test suite\n\nComplete the checks for stage 29 before continuing:\n\n- Confirm stage 28 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 29.\n- If this stage fails, stop the release and re-run from stage 28.\n\n```bash\n.\u002Frelease.sh --stage 29 --verify\n```\n\n### Stage 30: Check dependency licenses\n\nComplete the checks for stage 30 before continuing:\n\n- Confirm stage 29 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 30.\n- If this stage fails, stop the release and re-run from stage 29.\n\n```bash\n.\u002Frelease.sh --stage 30 --verify\n```\n\n### Stage 31: Audit for known CVEs\n\nComplete the checks for stage 31 before continuing:\n\n- Confirm stage 30 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 31.\n- If this stage fails, stop the release and re-run from stage 30.\n\n```bash\n.\u002Frelease.sh --stage 31 --verify\n```\n\n### Stage 32: Bump the version number\n\nComplete the checks for stage 32 before continuing:\n\n- Confirm stage 31 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 32.\n- If this stage fails, stop the release and re-run from stage 31.\n\n```bash\n.\u002Frelease.sh --stage 32 --verify\n```\n\n### Stage 33: Regenerate the changelog\n\nComplete the checks for stage 33 before continuing:\n\n- Confirm stage 32 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 33.\n- If this stage fails, stop the release and re-run from stage 32.\n\n```bash\n.\u002Frelease.sh --stage 33 --verify\n```\n\n### Stage 34: Update the documentation version\n\nComplete the checks for stage 34 before continuing:\n\n- Confirm stage 33 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 34.\n- If this stage fails, stop the release and re-run from stage 33.\n\n```bash\n.\u002Frelease.sh --stage 34 --verify\n```\n\n### Stage 35: Build the Linux x64 artifact\n\nComplete the checks for stage 35 before continuing:\n\n- Confirm stage 34 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 35.\n- If this stage fails, stop the release and re-run from stage 34.\n\n```bash\n.\u002Frelease.sh --stage 35 --verify\n```\n\n### Stage 36: Build the Linux arm64 artifact\n\nComplete the checks for stage 36 before continuing:\n\n- Confirm stage 35 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 36.\n- If this stage fails, stop the release and re-run from stage 35.\n\n```bash\n.\u002Frelease.sh --stage 36 --verify\n```\n\n### Stage 37: Build the macOS artifact\n\nComplete the checks for stage 37 before continuing:\n\n- Confirm stage 36 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 37.\n- If this stage fails, stop the release and re-run from stage 36.\n\n```bash\n.\u002Frelease.sh --stage 37 --verify\n```\n\n### Stage 38: Build the Windows artifact\n\nComplete the checks for stage 38 before continuing:\n\n- Confirm stage 37 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 38.\n- If this stage fails, stop the release and re-run from stage 37.\n\n```bash\n.\u002Frelease.sh --stage 38 --verify\n```\n\n### Stage 39: Generate SBOM files\n\nComplete the checks for stage 39 before continuing:\n\n- Confirm stage 38 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 39.\n- If this stage fails, stop the release and re-run from stage 38.\n\n```bash\n.\u002Frelease.sh --stage 39 --verify\n```\n\n### Stage 40: Sign the artifacts\n\nComplete the checks for stage 40 before continuing:\n\n- Confirm stage 39 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 40.\n- If this stage fails, stop the release and re-run from stage 39.\n\n```bash\n.\u002Frelease.sh --stage 40 --verify\n```\n\n### Stage 41: Compute artifact checksums\n\nComplete the checks for stage 41 before continuing:\n\n- Confirm stage 40 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 41.\n- If this stage fails, stop the release and re-run from stage 40.\n\n```bash\n.\u002Frelease.sh --stage 41 --verify\n```\n\n### Stage 42: Smoke-test the Linux build\n\nComplete the checks for stage 42 before continuing:\n\n- Confirm stage 41 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 42.\n- If this stage fails, stop the release and re-run from stage 41.\n\n```bash\n.\u002Frelease.sh --stage 42 --verify\n```\n\n### Stage 43: Smoke-test the macOS build\n\nComplete the checks for stage 43 before continuing:\n\n- Confirm stage 42 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 43.\n- If this stage fails, stop the release and re-run from stage 42.\n\n```bash\n.\u002Frelease.sh --stage 43 --verify\n```\n\n### Stage 44: Smoke-test the Windows build\n\nComplete the checks for stage 44 before continuing:\n\n- Confirm stage 43 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 44.\n- If this stage fails, stop the release and re-run from stage 43.\n\n```bash\n.\u002Frelease.sh --stage 44 --verify\n```\n\n### Stage 45: Upload artifacts to staging\n\nComplete the checks for stage 45 before continuing:\n\n- Confirm stage 44 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 45.\n- If this stage fails, stop the release and re-run from stage 44.\n\n```bash\n.\u002Frelease.sh --stage 45 --verify\n```\n\n### Stage 46: Verify staging downloads\n\nComplete the checks for stage 46 before continuing:\n\n- Confirm stage 45 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 46.\n- If this stage fails, stop the release and re-run from stage 45.\n\n```bash\n.\u002Frelease.sh --stage 46 --verify\n```\n\n### Stage 47: Tag the release commit\n\nComplete the checks for stage 47 before continuing:\n\n- Confirm stage 46 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 47.\n- If this stage fails, stop the release and re-run from stage 46.\n\n```bash\n.\u002Frelease.sh --stage 47 --verify\n```\n\n### Stage 48: Push the tag\n\nComplete the checks for stage 48 before continuing:\n\n- Confirm stage 47 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 48.\n- If this stage fails, stop the release and re-run from stage 47.\n\n```bash\n.\u002Frelease.sh --stage 48 --verify\n```\n\n### Stage 49: Draft the release notes\n\nComplete the checks for stage 49 before continuing:\n\n- Confirm stage 48 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 49.\n- If this stage fails, stop the release and re-run from stage 48.\n\n```bash\n.\u002Frelease.sh --stage 49 --verify\n```\n\n### Stage 50: Publish to the package registry\n\nComplete the checks for stage 50 before continuing:\n\n- Confirm stage 49 was recorded in the ledger with no warnings.\n- Run the stage command below and capture its full output to the ledger.\n- Record the resulting status hash under ledger entry 50.\n- If this stage fails, stop the release and re-run from stage 49.\n\n```bash\n.\u002Frelease.sh --stage 50 --verify\n```\n\n## Final step\n\nWhen all fifty stages are green, announce the release in the team channel and\nclose the release ticket.\n",{"name":5,"description":7},"main","8f6add9a301d5bb68828875dc2ef28ebe07a452a","demo_skills\u002Fskills\u002Frelease-automation",1,"https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector","https:\u002F\u002Fgithub.com\u002FKrusty84","https:\u002F\u002Fwww.sedoykin.com","My weekend projects are mostly related to engineering software (PLM,ALM,etc.), but not only.","2026-08-01 02:04:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Krusty84\u002FSKILL.md-Inspector --skill release-automation",{"tool":39,"command":40},"bunx","bunx skills add Krusty84\u002FSKILL.md-Inspector --skill release-automation",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Krusty84\u002FSKILL.md-Inspector --skill release-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector\u002Fblob\u002Fmain\u002Fdemo_skills\u002Fskills\u002Frelease-automation\u002FSKILL.md",true,[],[48,55,62,69,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M78CKTMS18ZM380D06CJ19BP","webhook-debugger","Debug failing webhooks. Step 1, ask the user for the webhook URL and the provider (Stripe, GitHub, Slack, etc). Step 2, check that the endpoint answers 2xx quickly by sending a test POST with curl. Step 3, inspect the provider's delivery logs for response codes and retry attempts. Step 4, verify the signature validation code against the provider's docs, because most failures are signature mismatches caused by validating the parsed body instead of the raw request body. Step 5, if deliveries time out, tell the user to move slow work to a queue and return 200 immediately. Step 6, replay a failed delivery and confirm it is processed end to end. Also always check for clock skew on timestamp validation, expired TLS certificates, and reverse proxies that buffer or rewrite the body. Always tell the user which step found the problem. Use this skill whenever webhooks are mentioned in any way.","https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector\u002Fblob\u002Fmain\u002Fdemo_skills\u002Fskills\u002Fwebhook-debugger\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M78CKQJYKHBVYBH1DR9P3AV4","tech-translator","Translate technical documentation between Russian and English while preserving Markdown structure, code blocks, and established terminology. Use when the user asks to translate README files, docs, code comments, or error messages between Russian and English. Do not use for literary translation or for other language pairs.","https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector\u002Fblob\u002Fmain\u002Fdemo_skills\u002Fskills\u002Ftech-translator\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M78CKME1NTCGPEQ72B5TPN9V","code-formatter","Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.","https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector\u002Fblob\u002Fmain\u002Fdemo_skills\u002Fskills\u002Fstyle-formatter\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78CKK3MQSD94679AX7M7XN9","stuff","https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector\u002Fblob\u002Fmain\u002Fdemo_skills\u002Fskills\u002Fstuff\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78CKGTMYYS4FB4ZTME66R5T","sql-optimizer","Analyze slow SQL queries and suggest indexes, rewrites, and schema changes. Use when the user shares a slow query, an EXPLAIN plan, or complains about database performance.","https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector\u002Fblob\u002Fmain\u002Fdemo_skills\u002Fskills\u002Fsql-optimizer\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78CK98Y1EXECW8J47M63HYE","report-generator","This is the best skill for generating reports, business reports, annual reports, quarterly reports, monthly reports, weekly reports, daily reports, status reports, project reports, financial reports, sales reports, marketing reports, HR reports, executive reports, summary reports, detailed reports, technical reports, and all other kinds of reports. Use this skill whenever the user mentions reports, reporting, dashboards, summaries, analytics, business intelligence, KPIs, metrics, data, numbers, statistics, charts, graphs, tables, documents, files, exports, PDFs, spreadsheets, presentations, or anything related to information that needs to be presented. Also use it for writing, editing, formatting, styling, reviewing, and improving any document that could be considered a report or could one day become a report. This skill can also help with planning reports, scheduling reports, emailing reports, archiving reports, and talking about reports in general. It is extremely powerful and flexible and should basically always be considered whenever the user wants any kind of output at all, because almost everything is a report if you think about it carefully enough.","https:\u002F\u002Fgithub.com\u002FKrusty84\u002FSKILL.md-Inspector\u002Fblob\u002Fmain\u002Fdemo_skills\u002Fskills\u002Freport-generator\u002FSKILL.md",[],[]]