[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCS49985G7JBQ0PGPW48D0":3,"skill-same:01M6MCS49985G7JBQ0PGPW48D0":111},{"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":28,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6MCS49985G7JBQ0PGPW48D0","technical-manuscript-verification",null,"Verify technical nonfiction manuscripts for runnable accuracy, including commands, configuration, code snippets, links, version drift, screenshots, prerequisites, security warnings, expected outputs, and reproducibility. Use when auditing self-hosting, DevOps, programming, infrastructure, data, security, or software tutorial drafts before beta reading, publication, or release.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"technical manuscript verification","verification","manuscript","technical","self","when","drafts","books","reading","technical-writing","software","commands","snippets","writing","drift","data","beta","release","code","infrastructure","security","2026-11-10 10:12:30",false,"---\nname: technical-manuscript-verification\ndescription: Verify technical nonfiction manuscripts for runnable accuracy, including commands, configuration, code snippets, links, version drift, screenshots, prerequisites, security warnings, expected outputs, and reproducibility. Use when auditing self-hosting, DevOps, programming, infrastructure, data, security, or software tutorial drafts before beta reading, publication, or release.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Technical Manuscript Verification\n  category: Writing\n  tags: writing,books,nonfiction,technical-writing,verification\n---\n\n# Technical Manuscript Verification\n\n## Core Lens\n\nTechnical nonfiction must work in the reader's environment, not just in the author's memory. Verification checks whether commands run, configs are coherent, screenshots match text, links still resolve, safety boundaries are clear, and the reader has enough context to recover from failure.\n\nUse this skill to audit:\n\n- Technical book chapters and tutorials.\n- Self-hosting and infrastructure guides.\n- Code snippets, shell commands, Docker Compose files, config examples, diagrams, and screenshots.\n- Claims that depend on current platform behavior or version-specific documentation.\n- Pre-beta or pre-publication technical accuracy.\n\n## Reference Routing\n\n| Need | Read |\n|------|------|\n| Verification concepts and terminology | `references\u002Fcore\u002Fknowledge.md` |\n| Audit rules and evidence standards | `references\u002Fcore\u002Frules.md` |\n| Example findings and verification tables | `references\u002Fcore\u002Fexamples.md` |\n| Fast verification checklist | `references\u002Fcore\u002Fchecklist.md` |\n| Step-by-step verification pass | `workflows\u002Fverify-technical-manuscript.md` |\n\n## Workflow\n\n### 1. Define The Verification Scope\n\nIdentify what needs verification:\n\n- Commands and code.\n- Config files and environment variables.\n- Installation and setup steps.\n- Screenshots, diagrams, and expected outputs.\n- Links and external references.\n- Safety, security, privacy, data loss, and cost warnings.\n\nUse a narrow pass when the manuscript is large.\n\n### 2. Build An Evidence Table\n\nFor each technical item, track:\n\n```text\nItem | Location | Assumption | Verification method | Result | Fix\n```\n\nDo not rely on plausibility when the item can be checked.\n\n### 3. Verify Against Real Or Simulated Environments\n\nPrefer running commands, linting configs, checking links, rendering examples, or consulting primary documentation. When execution is unsafe or impractical, state the assumption and the evidence still needed.\n\n### 4. Classify Findings By Reader Risk\n\nPrioritize:\n\n- Data loss, security exposure, privacy harm, or irreversible changes.\n- Commands that fail or produce different output.\n- Missing prerequisites that block readers.\n- Current-info drift from tool or platform changes.\n- Misleading screenshots or diagrams.\n\n### 5. Return Fixes The Author Can Apply\n\nRecommend exact changes:\n\n- Add prerequisite.\n- Change command or config.\n- Add expected output.\n- Add warning, rollback, or troubleshooting note.\n- Move volatile steps to a companion resource.\n- Mark claim for current-doc verification.\n\n## Output Format\n\nWhen verifying a manuscript, return:\n\n1. Verification scope and assumptions.\n2. Findings ordered by reader risk.\n3. Evidence table with pass\u002Ffail\u002Funtested status.\n4. Exact manuscript fixes.\n5. Items requiring current primary-source verification.\n6. Suggested beta-reader or expert-review checks.\n\n## Quality Bar\n\nBe concrete and evidence-driven. Distinguish \"verified,\" \"likely,\" \"untested,\" and \"unsafe to test here.\" Never imply that a technical instruction works unless it was actually checked or the limitation is clearly stated.\n","# Technical Manuscript Verification\n\n## Core Lens\n\nTechnical nonfiction must work in the reader's environment, not just in the author's memory. Verification checks whether commands run, configs are coherent, screenshots match text, links still resolve, safety boundaries are clear, and the reader has enough context to recover from failure.\n\nUse this skill to audit:\n\n- Technical book chapters and tutorials.\n- Self-hosting and infrastructure guides.\n- Code snippets, shell commands, Docker Compose files, config examples, diagrams, and screenshots.\n- Claims that depend on current platform behavior or version-specific documentation.\n- Pre-beta or pre-publication technical accuracy.\n\n## Reference Routing\n\n| Need | Read |\n|------|------|\n| Verification concepts and terminology | `references\u002Fcore\u002Fknowledge.md` |\n| Audit rules and evidence standards | `references\u002Fcore\u002Frules.md` |\n| Example findings and verification tables | `references\u002Fcore\u002Fexamples.md` |\n| Fast verification checklist | `references\u002Fcore\u002Fchecklist.md` |\n| Step-by-step verification pass | `workflows\u002Fverify-technical-manuscript.md` |\n\n## Workflow\n\n### 1. Define The Verification Scope\n\nIdentify what needs verification:\n\n- Commands and code.\n- Config files and environment variables.\n- Installation and setup steps.\n- Screenshots, diagrams, and expected outputs.\n- Links and external references.\n- Safety, security, privacy, data loss, and cost warnings.\n\nUse a narrow pass when the manuscript is large.\n\n### 2. Build An Evidence Table\n\nFor each technical item, track:\n\n```text\nItem | Location | Assumption | Verification method | Result | Fix\n```\n\nDo not rely on plausibility when the item can be checked.\n\n### 3. Verify Against Real Or Simulated Environments\n\nPrefer running commands, linting configs, checking links, rendering examples, or consulting primary documentation. When execution is unsafe or impractical, state the assumption and the evidence still needed.\n\n### 4. Classify Findings By Reader Risk\n\nPrioritize:\n\n- Data loss, security exposure, privacy harm, or irreversible changes.\n- Commands that fail or produce different output.\n- Missing prerequisites that block readers.\n- Current-info drift from tool or platform changes.\n- Misleading screenshots or diagrams.\n\n### 5. Return Fixes The Author Can Apply\n\nRecommend exact changes:\n\n- Add prerequisite.\n- Change command or config.\n- Add expected output.\n- Add warning, rollback, or troubleshooting note.\n- Move volatile steps to a companion resource.\n- Mark claim for current-doc verification.\n\n## Output Format\n\nWhen verifying a manuscript, return:\n\n1. Verification scope and assumptions.\n2. Findings ordered by reader risk.\n3. Evidence table with pass\u002Ffail\u002Funtested status.\n4. Exact manuscript fixes.\n5. Items requiring current primary-source verification.\n6. Suggested beta-reader or expert-review checks.\n\n## Quality Bar\n\nBe concrete and evidence-driven. Distinguish \"verified,\" \"likely,\" \"untested,\" and \"unsafe to test here.\" Never imply that a technical instruction works unless it was actually checked or the limitation is clearly stated.\n",{"name":5,"license":15,"metadata":55,"description":7,"compatibility":60},{"tags":56,"version":57,"category":58,"displayName":59},"writing,books,nonfiction,technical-writing,verification","0.1.0","Writing","Technical Manuscript Verification","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification",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":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill technical-manuscript-verification",{"tool":77,"command":78},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill technical-manuscript-verification",{"tool":80,"command":81},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill technical-manuscript-verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification\u002FSKILL.md",true,[85,91,95,99,103,107],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"agents\u002Fopenai.yaml","REFERENCE","参考文档",241,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification\u002Fagents\u002Fopenai.yaml",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fcore\u002Fchecklist.md",2166,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification\u002Freferences\u002Fcore\u002Fchecklist.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fcore\u002Fexamples.md",2812,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification\u002Freferences\u002Fcore\u002Fexamples.md",{"path":100,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fcore\u002Fknowledge.md",4031,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification\u002Freferences\u002Fcore\u002Fknowledge.md",{"path":104,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fcore\u002Frules.md",3033,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification\u002Freferences\u002Fcore\u002Frules.md",{"path":108,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":109,"sourceHtmlUrl":110},"workflows\u002Fverify-technical-manuscript.md",2555,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Ftechnical-manuscript-verification\u002Fworkflows\u002Fverify-technical-manuscript.md",[112,121,128,135,161,186],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":120},"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.","Apache-2.0","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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":120},"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":120},"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":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":50},"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",[],[142,143,144,145,146,147,148,149,150,151,152,34,153,154,155,156,157,158,159,160],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":50},"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",[],[168,169,170,156,171,172,173,174,175,176,177,178,179,180,147,181,182,183,184,185],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":116,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":199,"publishedAt":50},"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",[192,195,196],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":197,"categoryName":198,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[188,200,201,202,203,204,205,182,206,148,207,208,209,210,34,211,212,213,214,215],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]