[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MCQM3NJF9ZH1VC7D4WWV3W":3,"skill-same:01M6MCQM3NJF9ZH1VC7D4WWV3W":98},{"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":23,"publishedAt":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":61,"ownerHtmlUrl":62,"ownerBlogUrl":63,"ownerDescription":64,"updatedAt":65,"install":66,"resources":79},"01M6MCQM3NJF9ZH1VC7D4WWV3W","saas-documentation",null,"Plan and write SaaS documentation for managed services, continuous releases, provider\u002Fcustomer responsibility boundaries, UI\u002Fbrowser constraints, runbooks, support enablement, and release readiness. Use when documenting cloud products, hosted services, admin consoles, fleet-wide changes, service operations, incident or runbook procedures, SaaS release notes, customer-controlled settings, or internal docs that support customer experience.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fsaas-documentation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"saas documentation","documentation","saas","plan","when","managed","release readiness","developer-docs","runbooks","technical-writing","incident","releases","write","writing","browser","release","code","release notes","notes","support","customer","2026-11-10 10:12:30",false,"---\nname: saas-documentation\ndescription: Plan and write SaaS documentation for managed services, continuous releases, provider\u002Fcustomer responsibility boundaries, UI\u002Fbrowser constraints, runbooks, support enablement, and release readiness. Use when documenting cloud products, hosted services, admin consoles, fleet-wide changes, service operations, incident or runbook procedures, SaaS release notes, customer-controlled settings, or internal docs that support customer experience.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: SaaS Documentation\n  category: Writing\n  tags: developer-docs,technical-writing,documentation,saas,operations\n---\n\n# SaaS Documentation\n\nUse this skill to plan, draft, and review documentation for SaaS and managed-service products. It covers public customer docs and internal operational docs that affect the customer experience.\n\nThis skill is derived from paraphrased guidance in Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 25, \"Writing SaaS Documentation,\" Chapter 10, \"Maintaining Existing Content,\" Chapter 18, \"Working with Customer Support,\" and Chapter 2, \"Agile.\" Do not copy book prose into user outputs. Source: https:\u002F\u002Flink.springer.com\u002Fbook\u002F10.1007\u002F978-1-4842-7217-6\n\n## Quick Start\n\n1. Load `guidelines.md` to choose the smallest useful reference set.\n2. Identify whether the docs are public customer docs, internal service docs, release notes, runbooks, or support enablement.\n3. Define what the provider manages and what the customer controls.\n4. Use `workflows\u002Fplan-saas-docs.md` for customer-facing documentation plans.\n5. Use `workflows\u002Fcreate-saas-runbook.md` for operational or support procedures.\n6. Return customer impact, prerequisites, responsibilities, release timing, owners, and review needs.\n\n## Default Output\n\nWhen working on SaaS documentation, return:\n\n1. **Audience and surface** - customer, admin, support, operations, field, or internal team.\n2. **Responsibility boundary** - provider-managed, customer-controlled, shared, or unsupported.\n3. **Customer impact** - action required, risk, timing, permissions, billing, security, or availability.\n4. **Doc set recommendation** - public topic, release note, support article, runbook, enablement note, or escalation path.\n5. **Operational readiness** - owners, review, incident path, support signals, and update triggers.\n6. **Open questions** - unresolved behavior, launch timing, support process, or ownership.\n\n## Contents\n\n| Need | Start Here |\n|------|------------|\n| Understand SaaS documentation concepts | `references\u002Fcore\u002Fknowledge.md` |\n| Plan SaaS customer-facing docs | `workflows\u002Fplan-saas-docs.md` |\n| Create support or operations runbooks | `workflows\u002Fcreate-saas-runbook.md` |\n| Route by task or symptom | `guidelines.md` |\n\n## Core Posture\n\n- Treat documentation as part of the managed service.\n- Make provider and customer responsibilities explicit.\n- Document fleet-wide change with customer impact and action, not just feature description.\n- Treat internal runbooks and support enablement as customer-experience infrastructure.\n- Keep SaaS docs current with release, operations, and support signals.\n","# SaaS Documentation\n\nUse this skill to plan, draft, and review documentation for SaaS and managed-service products. It covers public customer docs and internal operational docs that affect the customer experience.\n\nThis skill is derived from paraphrased guidance in Christopher Gales and the Splunk Documentation Team's *The Product Is Docs: Writing Technical Documentation in a Product Development Group*, especially Chapter 25, \"Writing SaaS Documentation,\" Chapter 10, \"Maintaining Existing Content,\" Chapter 18, \"Working with Customer Support,\" and Chapter 2, \"Agile.\" Do not copy book prose into user outputs. Source: https:\u002F\u002Flink.springer.com\u002Fbook\u002F10.1007\u002F978-1-4842-7217-6\n\n## Quick Start\n\n1. Load `guidelines.md` to choose the smallest useful reference set.\n2. Identify whether the docs are public customer docs, internal service docs, release notes, runbooks, or support enablement.\n3. Define what the provider manages and what the customer controls.\n4. Use `workflows\u002Fplan-saas-docs.md` for customer-facing documentation plans.\n5. Use `workflows\u002Fcreate-saas-runbook.md` for operational or support procedures.\n6. Return customer impact, prerequisites, responsibilities, release timing, owners, and review needs.\n\n## Default Output\n\nWhen working on SaaS documentation, return:\n\n1. **Audience and surface** - customer, admin, support, operations, field, or internal team.\n2. **Responsibility boundary** - provider-managed, customer-controlled, shared, or unsupported.\n3. **Customer impact** - action required, risk, timing, permissions, billing, security, or availability.\n4. **Doc set recommendation** - public topic, release note, support article, runbook, enablement note, or escalation path.\n5. **Operational readiness** - owners, review, incident path, support signals, and update triggers.\n6. **Open questions** - unresolved behavior, launch timing, support process, or ownership.\n\n## Contents\n\n| Need | Start Here |\n|------|------------|\n| Understand SaaS documentation concepts | `references\u002Fcore\u002Fknowledge.md` |\n| Plan SaaS customer-facing docs | `workflows\u002Fplan-saas-docs.md` |\n| Create support or operations runbooks | `workflows\u002Fcreate-saas-runbook.md` |\n| Route by task or symptom | `guidelines.md` |\n\n## Core Posture\n\n- Treat documentation as part of the managed service.\n- Make provider and customer responsibilities explicit.\n- Document fleet-wide change with customer impact and action, not just feature description.\n- Treat internal runbooks and support enablement as customer-experience infrastructure.\n- Keep SaaS docs current with release, operations, and support signals.\n",{"name":5,"license":15,"metadata":50,"description":7,"compatibility":55},{"tags":51,"version":52,"category":53,"displayName":54},"developer-docs,technical-writing,documentation,saas,operations","0.1.0","Writing","SaaS Documentation","Codex, Claude Code, and other Agent Skills-compatible clients.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fsaas-documentation",490,"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 02:12:02",{"source":8,"skillName":5,"commands":67,"prompt":77,"zipAvailable":78},[68,71,74],{"tool":69,"command":70},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill saas-documentation",{"tool":72,"command":73},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill saas-documentation",{"tool":75,"command":76},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill saas-documentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fsaas-documentation\u002FSKILL.md",true,[80,86,90,94],{"path":81,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":85},"guidelines.md","REFERENCE","参考文档",2183,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fsaas-documentation\u002Fguidelines.md",{"path":87,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fcore\u002Fknowledge.md",7301,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fsaas-documentation\u002Freferences\u002Fcore\u002Fknowledge.md",{"path":91,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":92,"sourceHtmlUrl":93},"workflows\u002Fcreate-saas-runbook.md",3274,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fsaas-documentation\u002Fworkflows\u002Fcreate-saas-runbook.md",{"path":95,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":96,"sourceHtmlUrl":97},"workflows\u002Fplan-saas-docs.md",3139,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FLVTD-LLC\u002Fskills\u002Fskills\u002Fsaas-documentation\u002Fworkflows\u002Fplan-saas-docs.md",[99,108,115,122,148,173],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":107},"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":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":107},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":107},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":45},"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",[],[129,130,131,132,133,134,135,136,137,138,139,28,140,141,142,143,144,145,146,147],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":45},"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",[],[155,156,157,143,158,159,160,161,162,163,164,165,166,167,134,168,169,170,171,172],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":103,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":190,"publishedAt":45},"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",[179,184,187],{"categoryNo":180,"categoryName":181,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":185,"categoryName":186,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":188,"categoryName":189,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000010","后端与接口",[175,191,192,193,194,195,196,169,197,135,198,199,200,201,28,202,203,204,205,206],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]