{"id":"fe5659be-b78a-49ed-9d0a-fad6e51aa7a6","entityType":"agent","slug":"clawhub-kyro-ma-openapi-docs-generator","name":"Openapi Docs Generator","canonicalUrl":"https://www.xpersona.co/agent/clawhub-kyro-ma-openapi-docs-generator","canonicalPath":"/agent/clawhub-kyro-ma-openapi-docs-generator","generatedAt":"2026-10-09T16:07:19.323Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:09:31.605Z","emptyReason":null},"description":"Helps with Backend and platform teams need practical help gen...","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.9K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:openapi-docs-generator","sourceUrl":"https://clawhub.ai/kyro-ma/openapi-docs-generator","homepage":"https://clawhub.ai/kyro-ma/skills/openapi-docs-generator","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/kyro-ma/openapi-docs-generator","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/kyro-ma/skills/openapi-docs-generator","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":69,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Openapi Docs Generator technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:09:31.605Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:09:31.605Z","emptyReason":null},"stars":null,"forks":null,"downloads":2850,"packageName":null,"latestVersion":"0.0.0-20261009-045810","tractionLabel":"2.9K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:09:31.605Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T11:09:31.605Z","lastCrawledAt":"2026-10-09T11:09:31.605Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T11:09:31.605Z","lastVerifiedAt":null,"highlights":[{"version":"0.0.0-20261009-045810","createdAt":"2026-10-09T05:01:28.148Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for clarity and completeness. - Revised references/requirement-plan.md with new details or planning criteria. - Removed obsolete skill-card.md file for better maintainability.","fileCount":8,"zipByteSize":10789},{"version":"0.20260916.221748","createdAt":"2026-09-16T22:19:46.057Z","changelog":"- Updated documentation in both English (README.md) and Chinese (README.zh-CN.md) for clarity and completeness. - Improved and reorganized requirement and planning details in references/requirement-plan.md. - Removed outdated skill-card.md file.","fileCount":8,"zipByteSize":11637},{"version":"0.20260911.40430","createdAt":"2026-09-11T04:07:09.980Z","changelog":"- Source evidence expanded: now supported by 4 source families (was 3). - Updated demand description and evidence references in documentation files to reflect broader validation. - Removed legacy skill-card.md file. - General documentation improvements in both English and Chinese readme and skills files.","fileCount":8,"zipByteSize":11311},{"version":"0.20260910.52416","createdAt":"2026-09-10T05:27:22.658Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for clarity and completeness. - Revised references/requirement-plan.md for improved requirement tracking and planning details. - Removed outdated skill-card.md file.","fileCount":8,"zipByteSize":11123},{"version":"0.20260908.51704","createdAt":"2026-09-08T05:19:49.259Z","changelog":"- Updated requirement evidence to reference 3 source families (was 4) for validated demand. - Updated supporting documents (README and SKILL descriptions) to reflect the revised evidence. - Removed the redundant skill-card.md file. - No changes made to core workflow, outputs, or validation steps.","fileCount":8,"zipByteSize":11676},{"version":"0.20260907.40414","createdAt":"2026-09-07T04:06:27.029Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for clarity and completeness. - Revised planning details in references/requirement-plan.md. - Removed outdated skill-card.md file to streamline documentation. - No functional or workflow changes introduced; this is a documentation-focused update.","fileCount":8,"zipByteSize":11783},{"version":"0.20260906.40422","createdAt":"2026-09-06T04:06:55.455Z","changelog":"- Updated documentation in README.md and README.zh-CN.md for improved clarity. - Made revisions to references/requirement-plan.md to align with updated requirements. - Removed obsolete skill-card.md file.","fileCount":8,"zipByteSize":11590},{"version":"0.20260905.61641","createdAt":"2026-09-05T06:19:12.345Z","changelog":"- Updated evidence and description to reference 4 source families instead of 3. - Removed redundant file: skill-card.md. - Minor revisions in documentation files for accuracy and consistency. - No changes to core workflow or expected outputs.","fileCount":8,"zipByteSize":11518}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:openapi-docs-generator","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s17aeyv38nyj5fn7jtgzdj2yyx88405d:openapi-docs-generator` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/kyro-ma/openapi-docs-generator before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T16:07:19.318Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-kyro-ma-openapi-docs-generator/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T11:09:31.605Z","emptyReason":null},"readme":"Skill: Openapi Docs Generator\n\nOwner: kyro-ma\n\nSummary: Helps with Backend and platform teams need practical help gen...\n\nTags: latest:0.20260916.221748\n\nVersion history:\n\nv0.0.0-20261009-045810 | 2026-10-09T05:01:28.148Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Revised references/requirement-plan.md with new details or planning criteria.\n- Removed obsolete skill-card.md file for better maintainability.\n\nv0.20260916.221748 | 2026-09-16T22:19:46.057Z | auto\n\n- Updated documentation in both English (README.md) and Chinese (README.zh-CN.md) for clarity and completeness.\n- Improved and reorganized requirement and planning details in references/requirement-plan.md.\n- Removed outdated skill-card.md file.\n\nv0.20260911.40430 | 2026-09-11T04:07:09.980Z | auto\n\n- Source evidence expanded: now supported by 4 source families (was 3).\n- Updated demand description and evidence references in documentation files to reflect broader validation.\n- Removed legacy skill-card.md file.\n- General documentation improvements in both English and Chinese readme and skills files.\n\nv0.20260910.52416 | 2026-09-10T05:27:22.658Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Revised references/requirement-plan.md for improved requirement tracking and planning details.\n- Removed outdated skill-card.md file.\n\nv0.20260908.51704 | 2026-09-08T05:19:49.259Z | auto\n\n- Updated requirement evidence to reference 3 source families (was 4) for validated demand.\n- Updated supporting documents (README and SKILL descriptions) to reflect the revised evidence.\n- Removed the redundant skill-card.md file.\n- No changes made to core workflow, outputs, or validation steps.\n\nv0.20260907.40414 | 2026-09-07T04:06:27.029Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Revised planning details in references/requirement-plan.md.\n- Removed outdated skill-card.md file to streamline documentation.\n- No functional or workflow changes introduced; this is a documentation-focused update.\n\nv0.20260906.40422 | 2026-09-06T04:06:55.455Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Made revisions to references/requirement-plan.md to align with updated requirements.\n- Removed obsolete skill-card.md file.\n\nv0.20260905.61641 | 2026-09-05T06:19:12.345Z | auto\n\n- Updated evidence and description to reference 4 source families instead of 3.\n- Removed redundant file: skill-card.md.\n- Minor revisions in documentation files for accuracy and consistency.\n- No changes to core workflow or expected outputs.\n\nv0.20260904.60001 | 2026-09-04T06:03:07.867Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and accuracy.\n- Revised requirement and planning details in references/requirement-plan.md.\n- Removed deprecated documentation file: skill-card.md.\n\nv0.20260831.40551 | 2026-08-31T04:08:16.534Z | auto\n\n- Dropped one source family from validated demand and evidence count (now 12 signals across 3 source families).\n- Updated documentation in README and SKILL files to match new requirement evidence.\n- Removed the obsolete skill-card.md file.\n- No functional changes; documentation and evidence sources streamlined.\n\nv0.20260830.92238 | 2026-08-30T09:25:47.095Z | auto\n\n- Updated requirement and evidence to reference 4 source families instead of 3, reflecting broader demand validation.\n- Synchronized documentation (README, SKILL) to match the latest requirement updates.\n- Removed outdated skill-card.md to streamline documentation.\n- No workflow or feature changes; all user-facing behavior remains consistent.\n\nv0.20260829.40354 | 2026-08-29T04:06:36.952Z | auto\n\n- Updated evidence to reflect 3 source families instead of 4 in all documentation.\n- Removed the skill-card.md file.\n- Revised demand and evidence descriptions for clarity and consistency.\n- Improved documentation formatting and language in both English and Chinese files.\n\nv0.20260828.40337 | 2026-08-28T04:07:10.869Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and usability.\n- Improved requirement and planning details in references/requirement-plan.md.\n- Removed outdated skill-card.md file.\n\nv0.20260827.40448 | 2026-08-27T04:07:04.164Z | auto\n\n- Updated requirement evidence from 3 to 4 source families for broader validation.\n- Removed the obsolete skill-card.md file.\n- Refreshed README, SKILL, and reference documentation for clarity and alignment.\n- No functional workflow or capability changes to the core skill.\n\nv0.20260826.40329 | 2026-08-26T04:06:10.742Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and consistency.\n- Revised references/requirement-plan.md to align with current workflow and requirements.\n- Removed outdated skill-card.md file.\n\nv0.20260825.44155 | 2026-08-25T04:50:55.881Z | auto\n\n- Source families supporting the validated demand reduced from 4 to 3 in documentation and planning files.\n- Skill description and requirement sections updated to match the revised evidence and signals.\n- Removed the deprecated skill-card.md file.\n- All relevant READMEs and supporting docs updated for consistency with the latest demand analysis.\n\nv0.20260824.40429 | 2026-08-24T04:07:06.352Z | auto\n\n- Updated evidence to reflect support from 4 source families instead of 3.\n- Revised documentation and descriptions for improved clarity and accuracy.\n- Removed legacy file: skill-card.md.\n- Minor edits to references and readme files for consistency.\n\nv0.20260823.40325 | 2026-08-23T04:06:42.504Z | auto\n\n- Updated references to underlying demand evidence from 4 source families to 3, reflecting revised analysis in planning documents.\n- Removed the file skill-card.md.\n- Minor updates to documentation in both English and Chinese to ensure consistency with the latest requirement evidence.\n\nv0.20260822.135636 | 2026-08-22T13:58:59.135Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised references/requirement-plan.md for planning and evidence details.\n- Removed obsolete skill-card.md file.\n\nv0.20260821.52309 | 2026-08-21T05:28:21.880Z | auto\n\n- Updated requirement evidence to include 4 source families instead of 3, reflecting broader validation.\n- Adjusted descriptions and documentation (including SKILL files and README files) to match the new evidence and source count.\n- Removed the obsolete skill-card.md file for improved file organization.\n- General content refresh and minor clarifications to align with updated requirements.\n\nv0.20260819.45504 | 2026-08-19T05:02:03.271Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised requirement and planning details in references/requirement-plan.md.\n- Removed the outdated skill-card.md file.\n\nv0.20260818.40417 | 2026-08-18T04:06:51.159Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and usability.\n- Revised references/requirement-plan.md for improved planning detail.\n- Removed the outdated skill-card.md file.\n\nv0.20260817.40422 | 2026-08-17T04:06:52.979Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and accuracy.\n- Revised references/requirement-plan.md for improved planning details.\n- Removed obsolete skill-card.md file.\n\nv0.20260815.40440 | 2026-08-15T04:08:37.998Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised and expanded requirements and planning details in references/requirement-plan.md.\n- Removed the skill-card.md file to streamline documentation.\n\nv0.20260814.40500 | 2026-08-14T04:10:20.654Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity and usability.\n- Revised references/requirement-plan.md to align with current requirements and planning details.\n- Removed the skill-card.md file to streamline documentation.\n\nv0.20260813.40345 | 2026-08-13T04:06:33.201Z | auto\n\n- Updated evidence to reflect support from 3 source families instead of 4.\n- Adjusted description and requirement sections to match new evidence count.\n- Removed the file skill-card.md.\n- Documentation updated in README and SKILL files to align with evidence and requirements changes.\n\nv0.20260812.40408 | 2026-08-12T04:12:16.847Z | auto\n\n- Updated and clarified documentation in README.md and README.zh-CN.md.\n- Improved reference material in references/requirement-plan.md.\n- Removed obsolete skill-card.md file for better clarity and maintenance.\n\nv0.20260811.40534 | 2026-08-11T04:07:34.172Z | auto\n\n- Expanded evidence base from 3 to 4 source families in documentation and requirements.\n- Updated demand statement throughout to reference 4 source families.\n- Removed obsolete skill-card.md file.\n- Minor documentation updates for clarity across English and Chinese README and SKILL files.\n\nv0.20260810.40316 | 2026-08-10T04:05:44.220Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised references/requirement-plan.md to reflect current requirements and planning details.\n- Removed obsolete file: skill-card.md.\n- No changes to core workflow, validation steps, or triggers.\n\nv0.20260809.40514 | 2026-08-09T04:08:29.451Z | auto\n\n- Requirement sources updated from 4 to 3 source families (in English and Chinese docs).\n- Description revised to reflect new source family count.\n- Planning and evidence documentation updated for accuracy.\n- Removed outdated skill-card.md file for clarity and maintenance.\n\nv0.20260802.40421 | 2026-08-02T04:05:47.838Z | auto\n\n- Updated demand evidence to reference 4 source families instead of 3.\n- Synced all documentation files (README, SKILL) to reflect the revised evidence and description.\n- Removed obsolete documentation file: skill-card.md.\n\nv0.20260730.234524 | 2026-07-30T23:50:45.778Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Revised references/requirement-plan.md to reflect current requirements and evidence.\n- Removed obsolete skill-card.md file.\n\nv0.20260730.110348 | 2026-07-30T11:10:22.990Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and improved guidance.\n- Expanded and revised references/requirement-plan.md with additional planning and review details.\n- Removed the obsolete skill-card.md file.\n\nv0.20260730.10356 | 2026-07-30T01:12:06.783Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and improved guidance.\n- Expanded or revised planning details in references/requirement-plan.md.\n- Removed the file skill-card.md for simplification and to reduce redundancy.\n\nv0.20260730.3907 | 2026-07-30T00:42:56.887Z | auto\n\n- Evidence now comes from 3 source families (was 4) and documentation updated accordingly.\n- References to signals and requirement scope adjusted in all documentation files.\n- Localization files (README.zh-CN.md, SKILL.zh-CN.md) updated to match the new evidence and counts.\n- Obsolete skill-card.md removed.\n\nv0.20260729.2331 | 2026-07-29T00:26:11.564Z | auto\n\n- Updated source evidence from 3 to 4 source families in requirement description and metadata.\n- Updated demand evidence and summary to reflect 4 source families across all documentation files.\n- Removed redundant file: skill-card.md.\n- Improved consistency across README and internal documentation.\n\nv0.20260728.90410 | 2026-07-28T09:06:27.762Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and usability.\n- Revised references/requirement-plan.md with improved planning details.\n- Removed outdated skill-card.md file to streamline documentation.\n\nv0.20260728.40430 | 2026-07-28T04:10:06.320Z | auto\n\n- Removed the file skill-card.md.\n- No changes to skill functionality or workflow.\n- All user and developer-facing documentation remains within SKILL.md.\n\nv0.20260728.40429 | 2026-07-28T04:07:14.850Z | auto\n\n- Updated guide documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Improved planning details in references/requirement-plan.md.\n- Removed deprecated file: skill-card.md.\n\nv0.20260728.1730 | 2026-07-28T00:19:34.407Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity.\n- Revised content in references/requirement-plan.md.\n- Removed the skill-card.md file as part of documentation clean-up.\n\nv0.20260727.130301 | 2026-07-27T13:08:54.312Z | auto\n\n- Updated README and related documentation for improved clarity and localization.\n- Removed the skill-card.md file to streamline documentation.\n- No changes to core workflows, requirements, or validation processes.\n\nv0.20260727.80339 | 2026-07-27T08:09:14.730Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity.\n- Revised references/requirement-plan.md with improved planning and requirement details.\n- Removed the legacy file skill-card.md to streamline documentation.\n\nv0.20260727.30443 | 2026-07-27T03:06:33.169Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Expanded and refined the requirement plan in references/requirement-plan.md.\n- Removed the deprecated skill-card.md file to streamline the documentation set.\n\nv0.20260727.4640 | 2026-07-27T00:49:05.257Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for improved clarity and usability.\n- Revised references/requirement-plan.md with additional details and clarifications.\n- Removed the skill-card.md file to reduce redundancy.\n\nv0.20260726.70315 | 2026-07-26T07:05:48.697Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and usability.\n- Improved requirement details and review criteria in references/requirement-plan.md.\n- Removed the outdated skill-card.md file to streamline the repository.\n\nv0.20260726.20446 | 2026-07-26T02:11:53.454Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for greater clarity and accessibility.\n- Expanded reference and planning details in references/requirement-plan.md.\n- No changes to core functionality or workflow logic.\n\nv0.20260726.13716 | 2026-07-26T01:45:06.820Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and completeness.\n- Improved and refined requirement details in references/requirement-plan.md.\n- Removed obsolete skill-card.md file to streamline project structure.\n\nv0.20260725.110246 | 2026-07-25T11:04:46.542Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and consistency.\n- Removed the obsolete skill-card.md file to streamline the repository. \n- No changes to core functionality.\n\nv0.20260725.60451 | 2026-07-25T06:12:40.573Z | auto\n\n- Updated documentation in README.md and README.zh-CN.md for clarity and accuracy.\n- Revised references/requirement-plan.md with improved planning details.\n- Removed outdated skill-card.md file to streamline project files.\n\nv0.20260725.34436 | 2026-07-25T03:50:51.505Z | auto\n\n- Improved documentation in README.md and README.zh-CN.md for clarity and usability.\n- Updated requirement-plan reference for more detailed context.\n- Removed outdated skill-card.md file.\n\nArchive index:\n\nArchive v0.0.0-20261009-045810: 8 files, 10789 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3441b), README.zh-CN.md (3449b), references/requirement-plan.md (5327b), skill-card.md (1588b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (157b)\n\nFile v0.0.0-20261009-045810:SKILL.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  Help users with Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, openapi, swagger, api documentation, rest api, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Openapi Docs Generator\n\n## Requirement\n\nUse this skill to help API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers with:\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 4 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nExample trigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.0.0-20261009-045810:README.md\n\n# Openapi Docs Generator\n\n## Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 4 source families.\n\n## Evidence\n\n- csdn-search: [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=461466c6d53a45ea9c6ee05f55500679&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base7&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues: [Shared artist knowledge API tools for interviewers and other agents](https://github.com/xdjs/MusicNerdWeb/issues/1424)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search: [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search: [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues: [Web Ask About, discovery review, and interviewer evaluation/integration](https://github.com/xdjs/MusicNerdWeb/issues/1422)\n- hacker-news-search: [You said no MCP](https://news.ycombinator.com/item?id=49908820)\n- hacker-news-search: [You said no MCP](https://news.ycombinator.com/item?id=49913269)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nTrigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.0.0-20261009-045810:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"openapi-docs-generator\",\n  \"version\": \"0.0.0-20261009-045810\",\n  \"publishedAt\": 1791522088148\n}\n\nFile v0.0.0-20261009-045810:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nAPI developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 4 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 4; sources: csdn, github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- csdn-search (2026-03-13T00:00:00+00:00): [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=461466c6d53a45ea9c6ee05f55500679&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base7&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues (2026-10-05T15:59:08+00:00): [Shared artist knowledge API tools for interviewers and other agents](https://github.com/xdjs/MusicNerdWeb/issues/1424)\n- segmentfault-search (2026-10-09T04:58:37.582837+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-10-09T04:58:37.582837+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-10-09T04:58:37.582837+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-10-09T04:58:37.582837+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-10-09T04:58:37.583376+00:00): [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search (2026-10-09T04:58:37.583376+00:00): [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search (2026-10-09T04:58:37.583376+00:00): [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues (2026-10-04T15:40:39+00:00): [Web Ask About, discovery review, and interviewer evaluation/integration](https://github.com/xdjs/MusicNerdWeb/issues/1422)\n- hacker-news-search (2026-09-30T13:40:52+00:00): [You said no MCP](https://news.ycombinator.com/item?id=49908820)\n- hacker-news-search (2026-09-30T19:35:47+00:00): [You said no MCP](https://news.ycombinator.com/item?id=49913269)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, openapi, swagger, api documentation, rest api, developer experience\n\nTrigger sentences:\n\n- Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n\nFile v0.0.0-20261009-045810:README.zh-CN.md\n\n# Openapi Docs Generator\n\n## 需求\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 4 个来源类型。\n\n## 来源证据\n\n- csdn-search：[OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=461466c6d53a45ea9c6ee05f55500679&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base7&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues：[Shared artist knowledge API tools for interviewers and other agents](https://github.com/xdjs/MusicNerdWeb/issues/1424)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search：[OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search：[答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues：[Web Ask About, discovery review, and interviewer evaluation/integration](https://github.com/xdjs/MusicNerdWeb/issues/1422)\n- hacker-news-search：[You said no MCP](https://news.ycombinator.com/item?id=49908820)\n- hacker-news-search：[You said no MCP](https://news.ycombinator.com/item?id=49913269)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.0.0-20261009-045810:skill-card.md\n\n## Description:\n\nHelps backend and platform teams create, improve, and validate OpenAPI or Swagger documentation for REST APIs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nAPI developers, backend and platform teams, and maintainers use this skill to plan, produce, and check REST API documentation and related workflows.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad automatic triggers may invoke the skill for unrelated API design or backend coding questions.\n\nMitigation: Invoke it explicitly for OpenAPI or Swagger documentation tasks and check that the answer addresses the requested scope.\n\n## Reference(s):\n\n- [Requirement plan](artifact/references/requirement-plan.md)\n- [ClawHub skill release](https://clawhub.ai/kyro-ma/skills/openapi-docs-generator)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Markdown, Code, Checklists]\n\n**Output Format:** [Tailored text or Markdown, with code or verification commands when requested]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Includes assumptions, validation notes, and next steps when relevant]\n\n## Skill Version(s):\n\n0.0.0-20261009-045810 (source: ClawHub release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.0.0-20261009-045810:SKILL.zh-CN.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  帮助用户处理“Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, openapi, swagger, api documentation, rest api，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Openapi Docs Generator\n\n## 需求\n\n使用这个技能帮助以下用户群体：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 4 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n示例触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.0.0-20261009-045810:agents/openai.yaml\n\ninterface:\n  display_name: \"Openapi Docs Generator\"\n  short_description: \"Helps with Backend and platform teams need practical help gen...\"\n  default_prompt: \"Use $openapi-docs-generator to help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260916.221748: 8 files, 11637 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3530b), README.zh-CN.md (3538b), references/requirement-plan.md (5416b), skill-card.md (2778b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (153b)\n\nFile v0.20260916.221748:SKILL.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  Help users with Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, openapi, swagger, api documentation, rest api, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Openapi Docs Generator\n\n## Requirement\n\nUse this skill to help API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers with:\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 4 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nExample trigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260916.221748:README.md\n\n# Openapi Docs Generator\n\n## Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 4 source families.\n\n## Evidence\n\n- csdn-search: [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=52210e32186244829e3096b1a704f94e&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base1&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues: [feat(reachability): expand sound Tier-2 coverage and gate its accuracy](https://github.com/KKloudTarus/synapse-ce/issues/1038)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search: [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search: [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues: [Add Swagger @ApiTags and operation summaries to src/recommendations/recommendations.controller.ts](https://github.com/rinafcode/teachLink_backend/issues/1478)\n- github-issues: [Push updates to existing Google Wallet pass objects](https://github.com/los-verdes/card-losverd-es/issues/28)\n- hacker-news-search: [DeepSeek v4.1 Flash](https://news.ycombinator.com/item?id=49648802)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nTrigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260916.221748:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"openapi-docs-generator\",\n  \"version\": \"0.20260916.221748\",\n  \"publishedAt\": 1789597186057\n}\n\nFile v0.20260916.221748:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nAPI developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 4 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 4; sources: csdn, github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- csdn-search (2026-03-13T00:00:00+00:00): [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=52210e32186244829e3096b1a704f94e&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base1&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues (2026-09-12T15:48:31+00:00): [feat(reachability): expand sound Tier-2 coverage and gate its accuracy](https://github.com/KKloudTarus/synapse-ce/issues/1038)\n- segmentfault-search (2026-09-16T22:18:18.973510+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-16T22:18:18.973510+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-16T22:18:18.973510+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-16T22:18:18.973510+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-16T22:18:18.974013+00:00): [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search (2026-09-16T22:18:18.974013+00:00): [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search (2026-09-16T22:18:18.974013+00:00): [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues (2026-09-16T12:55:04+00:00): [Add Swagger @ApiTags and operation summaries to src/recommendations/recommendations.controller.ts](https://github.com/rinafcode/teachLink_backend/issues/1478)\n- github-issues (2026-09-16T20:25:49+00:00): [Push updates to existing Google Wallet pass objects](https://github.com/los-verdes/card-losverd-es/issues/28)\n- hacker-news-search (2026-09-10T19:09:17+00:00): [DeepSeek v4.1 Flash](https://news.ycombinator.com/item?id=49648802)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, openapi, swagger, api documentation, rest api, developer experience\n\nTrigger sentences:\n\n- Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n\nFile v0.20260916.221748:README.zh-CN.md\n\n# Openapi Docs Generator\n\n## 需求\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 4 个来源类型。\n\n## 来源证据\n\n- csdn-search：[OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=52210e32186244829e3096b1a704f94e&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base1&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues：[feat(reachability): expand sound Tier-2 coverage and gate its accuracy](https://github.com/KKloudTarus/synapse-ce/issues/1038)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search：[OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search：[答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues：[Add Swagger @ApiTags and operation summaries to src/recommendations/recommendations.controller.ts](https://github.com/rinafcode/teachLink_backend/issues/1478)\n- github-issues：[Push updates to existing Google Wallet pass objects](https://github.com/los-verdes/card-losverd-es/issues/28)\n- hacker-news-search：[DeepSeek v4.1 Flash](https://news.ycombinator.com/item?id=49648802)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260916.221748:skill-card.md\n\n## Description:\n\nHelps API developers, backend teams, developer-experience teams, and maintainers generate, improve, and validate OpenAPI or Swagger documentation for REST APIs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to turn API documentation requests into practical OpenAPI or Swagger workflows, artifacts, checklists, analyses, code changes, and verification notes.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Implicit invocation is enabled with broad OpenAPI, Swagger, REST API, and documentation triggers, so the skill may run on adjacent API-related prompts.\n\nMitigation: Use explicit invocation or narrow activation terms when a deployment needs tighter routing.\n\nRisk: The skill can propose documentation, code, shell commands, or configuration changes that may not match a service's actual behavior.\n\nMitigation: Review generated artifacts against the API implementation and run the verification commands or checks before publishing.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/openapi-docs-generator)\n- [OpenAPI RESTful API Design](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=52210e32186244829e3096b1a704f94e&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base1&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- [Swagger Bearer Token Question](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- [OpenAPI Interface Specification](https://segmentfault.com/a/1190000043968971)\n- [Swagger Base URL Question](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- [Swagger Controller Documentation Issue](https://github.com/rinafcode/teachLink_backend/issues/1478)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown, code snippets, shell commands, configuration examples, and concise guidance]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include reusable checklists, workflows, implementation steps, assumptions, verification commands, and follow-up risks.]\n\n## Skill Version(s):\n\n0.20260916.221748 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260916.221748:SKILL.zh-CN.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  帮助用户处理“Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, openapi, swagger, api documentation, rest api，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Openapi Docs Generator\n\n## 需求\n\n使用这个技能帮助以下用户群体：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 4 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n示例触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260916.221748:agents/openai.yaml\n\ninterface:\n  display_name: \"Openapi Docs Generator\"\n  short_description: \"Helps with Backend and platform teams need practical help gen...\"\n  default_prompt: \"Use $openapi-docs-generator to help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260911.40430: 8 files, 11311 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3440b), README.zh-CN.md (3448b), references/requirement-plan.md (5326b), skill-card.md (2566b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (152b)\n\nFile v0.20260911.40430:SKILL.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  Help users with Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, openapi, swagger, api documentation, rest api, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Openapi Docs Generator\n\n## Requirement\n\nUse this skill to help API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers with:\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 4 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nExample trigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260911.40430:README.md\n\n# Openapi Docs Generator\n\n## Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 4 source families.\n\n## Evidence\n\n- github-issues: [Complete private obsync activation and live acceptance](https://github.com/snaraj/platform/issues/364)\n- csdn-search: [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=f654b326475d437eb952da1219237dbd&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^control&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search: [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search: [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- hacker-news-search: [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search: [Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n- hacker-news-search: [Ask HN: Why do we need MCP?](https://news.ycombinator.com/item?id=49489825)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nTrigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260911.40430:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"openapi-docs-generator\",\n  \"version\": \"0.20260911.40430\",\n  \"publishedAt\": 1789099629980\n}\n\nFile v0.20260911.40430:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nAPI developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 4 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 4; sources: csdn, github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- github-issues (2026-09-08T23:07:30+00:00): [Complete private obsync activation and live acceptance](https://github.com/snaraj/platform/issues/364)\n- csdn-search (2026-03-13T00:00:00+00:00): [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=f654b326475d437eb952da1219237dbd&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^control&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- segmentfault-search (2026-09-11T04:05:36.444283+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-11T04:05:36.444283+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-11T04:05:36.444283+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-11T04:05:36.444283+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-11T04:05:36.444785+00:00): [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search (2026-09-11T04:05:36.444785+00:00): [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search (2026-09-11T04:05:36.444785+00:00): [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- hacker-news-search (2026-09-01T23:07:37+00:00): [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search (2026-09-01T16:55:48+00:00): [Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n- hacker-news-search (2026-08-29T13:37:22+00:00): [Ask HN: Why do we need MCP?](https://news.ycombinator.com/item?id=49489825)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, openapi, swagger, api documentation, rest api, developer experience\n\nTrigger sentences:\n\n- Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n\nFile v0.20260911.40430:README.zh-CN.md\n\n# Openapi Docs Generator\n\n## 需求\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 4 个来源类型。\n\n## 来源证据\n\n- github-issues：[Complete private obsync activation and live acceptance](https://github.com/snaraj/platform/issues/364)\n- csdn-search：[OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=f654b326475d437eb952da1219237dbd&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^control&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search：[OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search：[答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- hacker-news-search：[Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search：[Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n- hacker-news-search：[Ask HN: Why do we need MCP?](https://news.ycombinator.com/item?id=49489825)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260911.40430:skill-card.md\n\n## Description:\n\nHelps API developers and backend or platform teams generate, improve, and validate OpenAPI or Swagger documentation for REST APIs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, backend teams, platform teams, developer-experience teams, and maintainers use this skill to produce practical OpenAPI or Swagger documentation workflows, checklists, implementation support, and validation notes for REST APIs.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The trigger language is broad, so the skill may be invoked for some general API or developer-experience requests outside OpenAPI or Swagger documentation work.\n\nMitigation: Use explicit OpenAPI, Swagger, REST API documentation, or developer-experience routing terms when invoking the skill, and tighten invocation wording if precise routing matters.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/openapi-docs-generator)\n- [CSDN OpenAPI RESTful API Design](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=f654b326475d437eb952da1219237dbd&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^control&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- [SegmentFault OpenAPI Interface Specification](https://segmentfault.com/a/1190000043968971)\n- [SegmentFault Swagger Bearer Authentication Answer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- [SegmentFault Swagger Base URL Answer](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown or plain text with optional code blocks, checklists, commands, and configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Tailored to the user's API documentation inputs and constraints; no independent tool execution is required by the skill artifact.]\n\n## Skill Version(s):\n\n0.20260911.40430 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260911.40430:SKILL.zh-CN.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  帮助用户处理“Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, openapi, swagger, api documentation, rest api，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Openapi Docs Generator\n\n## 需求\n\n使用这个技能帮助以下用户群体：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 4 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n示例触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260911.40430:agents/openai.yaml\n\ninterface:\n  display_name: \"Openapi Docs Generator\"\n  short_description: \"Helps with Backend and platform teams need practical help gen...\"\n  default_prompt: \"Use $openapi-docs-generator to help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260910.52416: 8 files, 11123 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3453b), README.zh-CN.md (3461b), references/requirement-plan.md (5331b), skill-card.md (2533b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (152b)\n\nFile v0.20260910.52416:SKILL.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  Help users with Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, openapi, swagger, api documentation, rest api, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Openapi Docs Generator\n\n## Requirement\n\nUse this skill to help API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers with:\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nExample trigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260910.52416:README.md\n\n# Openapi Docs Generator\n\n## Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- csdn-search: [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=eea9cc668d464518b70a9b88ff71bed2&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base8&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search: [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search: [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- hacker-news-search: [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search: [Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n- hacker-news-search: [Ask HN: Why do we need MCP?](https://news.ycombinator.com/item?id=49489825)\n- hacker-news-search: [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49568902)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nTrigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260910.52416:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"openapi-docs-generator\",\n  \"version\": \"0.20260910.52416\",\n  \"publishedAt\": 1789018042658\n}\n\nFile v0.20260910.52416:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nAPI developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: csdn, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- csdn-search (2026-03-13T00:00:00+00:00): [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=eea9cc668d464518b70a9b88ff71bed2&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base8&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- segmentfault-search (2026-09-10T05:25:27.918177+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-10T05:25:27.918177+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-10T05:25:27.918177+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-10T05:25:27.918177+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-10T05:25:27.918177+00:00): [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search (2026-09-10T05:25:27.918177+00:00): [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search (2026-09-10T05:25:27.918177+00:00): [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- hacker-news-search (2026-09-01T23:07:37+00:00): [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search (2026-09-01T16:55:48+00:00): [Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n- hacker-news-search (2026-08-29T13:37:22+00:00): [Ask HN: Why do we need MCP?](https://news.ycombinator.com/item?id=49489825)\n- hacker-news-search (2026-09-04T19:11:41+00:00): [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49568902)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, openapi, swagger, api documentation, rest api, developer experience\n\nTrigger sentences:\n\n- Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n\nFile v0.20260910.52416:README.zh-CN.md\n\n# Openapi Docs Generator\n\n## 需求\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- csdn-search：[OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=eea9cc668d464518b70a9b88ff71bed2&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base8&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search：[OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search：[答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- hacker-news-search：[Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search：[Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n- hacker-news-search：[Ask HN: Why do we need MCP?](https://news.ycombinator.com/item?id=49489825)\n- hacker-news-search：[Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49568902)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260910.52416:skill-card.md\n\n## Description:\n\nHelps API developers, backend teams, developer-experience teams, and maintainers generate, improve, and validate OpenAPI or Swagger documentation for REST APIs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineering teams use this skill to turn REST API documentation requests into practical workflows, checklists, analysis, code changes, or validation steps for OpenAPI and Swagger specs.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill may activate for broad OpenAPI, Swagger, REST API, or developer-experience phrasing.\n\nMitigation: Invoke it explicitly when API documentation help is intended, and confirm that generated guidance matches the user's API stack and documentation goals.\n\nRisk: Generated API documentation or validation advice could be incomplete or mismatched to the service contract.\n\nMitigation: Review generated artifacts against the source API implementation and run OpenAPI or Swagger validation before publishing.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [OpenAPI RESTful API Design](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=eea9cc668d464518b70a9b88ff71bed2&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base8&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- [OpenAPI Interface Specification](https://segmentfault.com/a/1190000043968971)\n- [Swagger Bearer Token Answer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- [Swagger Base URL Answer](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with optional code, shell command, and configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include assumptions, validation notes, remaining risks, and follow-up work when useful.]\n\n## Skill Version(s):\n\n0.20260910.52416 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260910.52416:SKILL.zh-CN.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  帮助用户处理“Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, openapi, swagger, api documentation, rest api，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Openapi Docs Generator\n\n## 需求\n\n使用这个技能帮助以下用户群体：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n示例触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260910.52416:agents/openai.yaml\n\ninterface:\n  display_name: \"Openapi Docs Generator\"\n  short_description: \"Helps with Backend and platform teams need practical help gen...\"\n  default_prompt: \"Use $openapi-docs-generator to help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260908.51704: 8 files, 11676 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3663b), README.zh-CN.md (3671b), references/requirement-plan.md (5515b), skill-card.md (2450b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (152b)\n\nFile v0.20260908.51704:SKILL.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  Help users with Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, openapi, swagger, api documentation, rest api, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Openapi Docs Generator\n\n## Requirement\n\nUse this skill to help API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers with:\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 3 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nExample trigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260908.51704:README.md\n\n# Openapi Docs Generator\n\n## Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 3 source families.\n\n## Evidence\n\n- csdn-search: [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=1b20ebba333544c7bc2c66c7f9838fe5&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base8&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues: [[2.1.0][EPIC] Source-aware Contract Diff MVP](https://github.com/albert-einshutoin/cdn-security-framework/issues/531)\n- github-issues: [[R0][EPIC-01] Secured platform foundation](https://github.com/APReddy-AutoBotz/Project-Delivery-Agent/issues/5)\n- github-issues: [dnse: NORMAL-book amend allows ONE changed field per call — combined price+qty modify 400s (INVALID_INPUT); _amend must split into two sequential edits](https://github.com/rubycell/pynecore/issues/86)\n- github-issues: [dnse: per-bar order updates silently do not reach the conditional book — amend-500 parks and the venue keeps STALE levels (trailing entries AND trailing stops)](https://github.com/rubycell/pynecore/issues/85)\n- github-issues: [[2.0.0][RELEASE] RC GO後にVersion・Changelog・公開・Rollbackを完了する](https://github.com/albert-einshutoin/cdn-security-framework/issues/571)\n- github-issues: [Standardized API Response Schemas](https://github.com/nensii21/devlink/issues/1484)\n- github-issues: [feat(metrics): expose latest SMART self-test status](https://github.com/Starosdev/scrutiny/issues/830)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nTrigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260908.51704:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"openapi-docs-generator\",\n  \"version\": \"0.20260908.51704\",\n  \"publishedAt\": 1788844789259\n}\n\nFile v0.20260908.51704:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nAPI developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 3 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 3; sources: csdn, github, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- csdn-search (2026-03-13T00:00:00+00:00): [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=1b20ebba333544c7bc2c66c7f9838fe5&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base8&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues (2026-08-25T12:50:32+00:00): [[2.1.0][EPIC] Source-aware Contract Diff MVP](https://github.com/albert-einshutoin/cdn-security-framework/issues/531)\n- github-issues (2026-09-06T09:37:14+00:00): [[R0][EPIC-01] Secured platform foundation](https://github.com/APReddy-AutoBotz/Project-Delivery-Agent/issues/5)\n- github-issues (2026-09-08T03:24:26+00:00): [dnse: NORMAL-book amend allows ONE changed field per call — combined price+qty modify 400s (INVALID_INPUT); _amend must split into two sequential edits](https://github.com/rubycell/pynecore/issues/86)\n- github-issues (2026-09-08T03:17:54+00:00): [dnse: per-bar order updates silently do not reach the conditional book — amend-500 parks and the venue keeps STALE levels (trailing entries AND trailing stops)](https://github.com/rubycell/pynecore/issues/85)\n- github-issues (2026-08-25T12:58:50+00:00): [[2.0.0][RELEASE] RC GO後にVersion・Changelog・公開・Rollbackを完了する](https://github.com/albert-einshutoin/cdn-security-framework/issues/571)\n- github-issues (2026-08-31T15:12:42+00:00): [Standardized API Response Schemas](https://github.com/nensii21/devlink/issues/1484)\n- github-issues (2026-09-08T05:00:32+00:00): [feat(metrics): expose latest SMART self-test status](https://github.com/Starosdev/scrutiny/issues/830)\n- segmentfault-search (2026-09-08T05:17:45.182806+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-08T05:17:45.182806+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-08T05:17:45.182806+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-08T05:17:45.182806+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, openapi, swagger, api documentation, rest api, developer experience\n\nTrigger sentences:\n\n- Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n\nFile v0.20260908.51704:README.zh-CN.md\n\n# Openapi Docs Generator\n\n## 需求\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 3 个来源类型。\n\n## 来源证据\n\n- csdn-search：[OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=1b20ebba333544c7bc2c66c7f9838fe5&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base8&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues：[[2.1.0][EPIC] Source-aware Contract Diff MVP](https://github.com/albert-einshutoin/cdn-security-framework/issues/531)\n- github-issues：[[R0][EPIC-01] Secured platform foundation](https://github.com/APReddy-AutoBotz/Project-Delivery-Agent/issues/5)\n- github-issues：[dnse: NORMAL-book amend allows ONE changed field per call — combined price+qty modify 400s (INVALID_INPUT); _amend must split into two sequential edits](https://github.com/rubycell/pynecore/issues/86)\n- github-issues：[dnse: per-bar order updates silently do not reach the conditional book — amend-500 parks and the venue keeps STALE levels (trailing entries AND trailing stops)](https://github.com/rubycell/pynecore/issues/85)\n- github-issues：[[2.0.0][RELEASE] RC GO後にVersion・Changelog・公開・Rollbackを完了する](https://github.com/albert-einshutoin/cdn-security-framework/issues/571)\n- github-issues：[Standardized API Response Schemas](https://github.com/nensii21/devlink/issues/1484)\n- github-issues：[feat(metrics): expose latest SMART self-test status](https://github.com/Starosdev/scrutiny/issues/830)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260908.51704:skill-card.md\n\n## Description:\n\nHelps API developers generate, improve, and validate OpenAPI or Swagger documentation for REST APIs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, backend teams, developer-experience teams, and API maintainers use this skill to turn REST API context into practical OpenAPI or Swagger documentation workflows, checklists, implementation support, and validation guidance.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill uses broad API-related auto-activation language and may trigger on general API prompts.\n\nMitigation: Use explicit invocation for OpenAPI or Swagger documentation tasks and review routing settings if accidental activation would disrupt the agent workflow.\n\nRisk: Generated API documentation guidance can be incomplete or misaligned with the actual service behavior.\n\nMitigation: Validate generated OpenAPI or Swagger changes against the source implementation, representative requests and responses, and an OpenAPI linter before publication.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub Skill Page](https://clawhub.ai/kyro-ma/skills/openapi-docs-generator)\n- [OpenAPI RESTful API Design](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=1b20ebba333544c7bc2c66c7f9838fe5&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base8&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- [Standardized API Response Schemas](https://github.com/nensii21/devlink/issues/1484)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown responses with optional code, shell command, checklist, and configuration snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include assumptions, validation notes, and follow-up risks when useful]\n\n## Skill Version(s):\n\n0.20260908.51704 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260908.51704:SKILL.zh-CN.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  帮助用户处理“Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, openapi, swagger, api documentation, rest api，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Openapi Docs Generator\n\n## 需求\n\n使用这个技能帮助以下用户群体：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 3 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 3 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n示例触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260908.51704:agents/openai.yaml\n\ninterface:\n  display_name: \"Openapi Docs Generator\"\n  short_description: \"Helps with Backend and platform teams need practical help gen...\"\n  default_prompt: \"Use $openapi-docs-generator to help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260907.40414: 8 files, 11783 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3600b), README.zh-CN.md (3608b), references/requirement-plan.md (5486b), skill-card.md (2675b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (152b)\n\nFile v0.20260907.40414:SKILL.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  Help users with Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, openapi, swagger, api documentation, rest api, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Openapi Docs Generator\n\n## Requirement\n\nUse this skill to help API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers with:\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 4 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nExample trigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260907.40414:README.md\n\n# Openapi Docs Generator\n\n## Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 4 source families.\n\n## Evidence\n\n- csdn-search: [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=764f1d2eb6bf44bb8e721571b9551f1c&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base4&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues: [Measure opportunity effectiveness across review and downstream outcomes](https://github.com/sgajbi/lotus-idea/issues/1156)\n- github-issues: [docs(DEN-3828): peer authorities, parity-approved Contract IR, and downstream Protobuf/gRPC/Connect/tRPC](https://github.com/ORESoftware/typespec-json-schema-validator/issues/20)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search: [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search: [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues: [feature request: Add MangaBaka as an alternative/fallback manga mapping source](https://github.com/bigspawn/anilist-mal-sync/issues/97)\n- hacker-news-search: [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nTrigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260907.40414:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"openapi-docs-generator\",\n  \"version\": \"0.20260907.40414\",\n  \"publishedAt\": 1788753987029\n}\n\nFile v0.20260907.40414:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nAPI developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 4 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 4; sources: csdn, github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- csdn-search (2026-03-13T00:00:00+00:00): [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=764f1d2eb6bf44bb8e721571b9551f1c&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base4&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues (2026-08-30T06:14:11+00:00): [Measure opportunity effectiveness across review and downstream outcomes](https://github.com/sgajbi/lotus-idea/issues/1156)\n- github-issues (2026-09-07T00:14:28+00:00): [docs(DEN-3828): peer authorities, parity-approved Contract IR, and downstream Protobuf/gRPC/Connect/tRPC](https://github.com/ORESoftware/typespec-json-schema-validator/issues/20)\n- segmentfault-search (2026-09-07T04:05:04.734853+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-07T04:05:04.734853+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-07T04:05:04.734853+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-07T04:05:04.734853+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-07T04:05:04.735542+00:00): [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search (2026-09-07T04:05:04.735542+00:00): [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search (2026-09-07T04:05:04.735542+00:00): [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues (2026-09-07T03:52:45+00:00): [feature request: Add MangaBaka as an alternative/fallback manga mapping source](https://github.com/bigspawn/anilist-mal-sync/issues/97)\n- hacker-news-search (2026-09-01T23:07:37+00:00): [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, openapi, swagger, api documentation, rest api, developer experience\n\nTrigger sentences:\n\n- Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n\nFile v0.20260907.40414:README.zh-CN.md\n\n# Openapi Docs Generator\n\n## 需求\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 4 个来源类型。\n\n## 来源证据\n\n- csdn-search：[OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=764f1d2eb6bf44bb8e721571b9551f1c&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base4&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues：[Measure opportunity effectiveness across review and downstream outcomes](https://github.com/sgajbi/lotus-idea/issues/1156)\n- github-issues：[docs(DEN-3828): peer authorities, parity-approved Contract IR, and downstream Protobuf/gRPC/Connect/tRPC](https://github.com/ORESoftware/typespec-json-schema-validator/issues/20)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search：[OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search：[答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues：[feature request: Add MangaBaka as an alternative/fallback manga mapping source](https://github.com/bigspawn/anilist-mal-sync/issues/97)\n- hacker-news-search：[Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260907.40414:skill-card.md\n\n## Description:\n\nHelps API developers and platform teams generate, improve, and validate OpenAPI or Swagger documentation for REST APIs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, backend teams, developer-experience teams, and maintainers use this skill to create, improve, and review API documentation so REST services are easier for other engineers to understand and consume.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad activation wording could route vague API documentation requests to this skill when another workflow would fit better.\n\nMitigation: Confirm the user's desired API documentation outcome, available inputs, constraints, and success criteria before producing artifacts.\n\nRisk: Generated OpenAPI or Swagger guidance may be incomplete, stale, or inconsistent with the user's service behavior.\n\nMitigation: Validate outputs against the source API implementation, examples, and stated review criteria before adoption.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [OpenAPI specification: RESTful API design](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=764f1d2eb6bf44bb8e721571b9551f1c&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base4&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- [Contract IR and downstream API documentation issue](https://github.com/ORESoftware/typespec-json-schema-validator/issues/20)\n- [Swagger Bearer token discussion](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- [OpenAPI interface specification article](https://segmentfault.com/a/1190000043968971)\n- [Swagger base URL discussion](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown, with code blocks or command snippets when implementation support is requested]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include checklists, workflow steps, assumptions, validation notes, and follow-up risks.]\n\n## Skill Version(s):\n\n0.20260907.40414 (source: release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260907.40414:SKILL.zh-CN.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  帮助用户处理“Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, openapi, swagger, api documentation, rest api，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Openapi Docs Generator\n\n## 需求\n\n使用这个技能帮助以下用户群体：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 4 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n示例触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260907.40414:agents/openai.yaml\n\ninterface:\n  display_name: \"Openapi Docs Generator\"\n  short_description: \"Helps with Backend and platform teams need practical help gen...\"\n  default_prompt: \"Use $openapi-docs-generator to help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\"\n\npolicy:\n  allow_implicit_invocation: true\n\nArchive v0.20260906.40422: 8 files, 11590 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3499b), README.zh-CN.md (3507b), references/requirement-plan.md (5385b), skill-card.md (2724b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (152b)\n\nFile v0.20260906.40422:SKILL.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  Help users with Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, openapi, swagger, api documentation, rest api, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Openapi Docs Generator\n\n## Requirement\n\nUse this skill to help API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers with:\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 4 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nExample trigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\nFile v0.20260906.40422:README.md\n\n# Openapi Docs Generator\n\n## Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 4 source families.\n\n## Evidence\n\n- csdn-search: [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=d4ffa243ecee43f58af4cab6b0f6b28d&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^control&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues: [The PM agent — the upper pipeline as a headless role with two rituals](https://github.com/yellow-robots/factory/issues/465)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search: [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search: [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues: [🏗️ Setup Projek API Toko Bangunan — Fitur Produk](https://github.com/rajamasker07/toko-bangunan-api/issues/1)\n- hacker-news-search: [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search: [Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nTrigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## Files\n\n- `SKILL.md`: English skill instructions.\n- `SKILL.zh-CN.md`: Chinese skill instructions.\n- `README.md`: English user-facing guide.\n- `README.zh-CN.md`: Chinese user-facing guide.\n\nFile v0.20260906.40422:_meta.json\n\n{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"openapi-docs-generator\",\n  \"version\": \"0.20260906.40422\",\n  \"publishedAt\": 1788667615455\n}\n\nFile v0.20260906.40422:references/requirement-plan.md\n\n# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nAPI developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 4 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 4; sources: csdn, github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- csdn-search (2026-03-13T00:00:00+00:00): [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=d4ffa243ecee43f58af4cab6b0f6b28d&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^control&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues (2026-09-05T10:04:31+00:00): [The PM agent — the upper pipeline as a headless role with two rituals](https://github.com/yellow-robots/factory/issues/465)\n- segmentfault-search (2026-09-06T04:05:09.533838+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-09-06T04:05:09.533838+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-09-06T04:05:09.533838+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-09-06T04:05:09.533838+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-09-06T04:05:09.534341+00:00): [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search (2026-09-06T04:05:09.534341+00:00): [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search (2026-09-06T04:05:09.534341+00:00): [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues (2026-09-05T12:26:12+00:00): [🏗️ Setup Projek API Toko Bangunan — Fitur Produk](https://github.com/rajamasker07/toko-bangunan-api/issues/1)\n- hacker-news-search (2026-09-01T23:07:37+00:00): [Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search (2026-09-01T16:55:48+00:00): [Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n\n## How The Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Executable Implementation Plan\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Review Criteria\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Usage Signals\n\nKeywords: software-and-data, openapi, swagger, api documentation, rest api, developer experience\n\nTrigger sentences:\n\n- Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n- Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.\n\nFile v0.20260906.40422:README.zh-CN.md\n\n# Openapi Docs Generator\n\n## 需求\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 4 个来源类型。\n\n## 来源证据\n\n- csdn-search：[OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=d4ffa243ecee43f58af4cab6b0f6b28d&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^control&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues：[The PM agent — the upper pipeline as a headless role with two rituals](https://github.com/yellow-robots/factory/issues/465)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search：[OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search：[答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues：[🏗️ Setup Projek API Toko Bangunan — Fitur Produk](https://github.com/rajamasker07/toko-bangunan-api/issues/1)\n- hacker-news-search：[Ask HN: Who wants to be hired? (September 2026)](https://news.ycombinator.com/item?id=49529516)\n- hacker-news-search：[Play Store blocks AuroraStore, hurting GrapheneOS users](https://news.ycombinator.com/item?id=49524639)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## 文件\n\n- `SKILL.md`：英文版技能说明。\n- `SKILL.zh-CN.md`：中文版技能说明。\n- `README.md`：英文版用户说明。\n- `README.zh-CN.md`：中文版用户说明。\n\nFile v0.20260906.40422:skill-card.md\n\n## Description:\n\nHelps API developers generate, improve, and validate OpenAPI or Swagger documentation for REST APIs.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[kyro-ma](https://clawhub.ai/user/kyro-ma)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, backend teams, developer-experience teams, and maintainers use this skill to create practical OpenAPI or Swagger documentation workflows, artifacts, review checklists, implementation support, and validation steps for REST APIs.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Broad trigger wording and implicit invocation may make the skill appear for loosely related backend or API documentation requests.\n\nMitigation: Confirm the user wants OpenAPI or Swagger documentation support when the request is ambiguous.\n\nRisk: Generated API documentation guidance can be incomplete or inconsistent with the actual service behavior if endpoint details, schemas, or authentication requirements are missing.\n\nMitigation: Validate outputs against the service implementation, OpenAPI validators, and project-specific review criteria before publishing.\n\n## Reference(s):\n\n- [Requirement Plan](references/requirement-plan.md)\n- [ClawHub skill page](https://clawhub.ai/kyro-ma/skills/openapi-docs-generator)\n- [OpenAPI RESTful API design demand signal](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=d4ffa243ecee43f58af4cab6b0f6b28d&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^control&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- [OpenAPI specification maintenance demand signal](https://segmentfault.com/a/1190000043968971)\n- [Swagger bearer-token documentation demand signal](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- [Swagger base URL documentation demand signal](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown with optional code blocks, shell commands, checklists, and configuration examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [May include assumptions, validation notes, remaining risks, and next-step guidance when helpful.]\n\n## Skill Version(s):\n\n0.20260906.40422 (source: release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v0.20260906.40422:SKILL.zh-CN.md\n\n---\nname: openapi-docs-generator\ndescription: >-\n  帮助用户处理“Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.”。当用户提出 software-and-data, openapi, swagger, api documentation, rest api，或需要围绕该需求获得实用流程、产物、检查清单、分析或实现支持时使用。\n---\n\n# Openapi Docs Generator\n\n## 需求\n\n使用这个技能帮助以下用户群体：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n需求评分：100/100（需求强度 `70/70`，本地可执行性 `30/30`）。\n证据：12 条信号，覆盖 4 个来源类型。\n\n如需查看来源证据、执行计划或评审标准，请阅读 `references/requirement-plan.md`。\n\n## 工作流程\n\n1. 重新说明用户想要的结果、限制、已有输入和成功标准。\n2. 检查技术限制，提出实现步骤，并在涉及代码或数据时包含测试或验证方法。\n3. 只有当缺失信息会明显改变输出时才提问；否则先做合理假设并继续推进。\n4. 保持本地硬件友好：优先使用脚本、模板、检查清单、小模型或 CPU 可承受的流程，避免依赖云端专用资源或大规模训练。\n5. 产出用户需要的文档、流程、清单、分析、代码修改或决策支持。\n6. 对照成功标准检查结果，并列出剩余风险或后续事项。\n\n## 预期输出\n\n- 针对用户当前情境的定制回答或产物。\n- 当任务可复用时，提供检查清单或工作流程。\n- 说明结果如何被检查的验证备注。\n\n## 验证\n\n- 输出直接回应发现的原始需求。\n- 用户不需要阅读原始来源帖子也能采取行动。\n- 假设、限制和所需输入清晰可见。\n- 在有帮助时，最终回复包含简短的使用说明或下一步建议。\n\n## 触发方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n示例触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or S\n\nArchive v0.20260905.61641: 8 files, 11518 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3545b), README.zh-CN.md (3553b), references/requirement-plan.md (5431b), skill-card.md (2383b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (152b)\n\nArchive v0.20260904.60001: 8 files, 11991 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3636b), README.zh-CN.md (3644b), references/requirement-plan.md (5509b), skill-card.md (3004b), SKILL.md (3158b), SKILL.zh-CN.md (3015b), _meta.json (152b)\n\nArchive v0.20260831.40551: 8 files, 11244 bytes\n\nFiles: agents/openai.yaml (364b), README.md (3206b), README.zh-CN.md (3214b), references/requirement-plan.md (5072b), skill-card.md (3440b...","readmeExcerpt":"Skill: Openapi Docs Generator Owner: kyro-ma Summary: Helps with Backend and platform teams need practical help gen... Tags: latest:0.20260916.221748 Version history: v0.0.0-20261009-045810 | 2026-10-09T05:01:28.148Z | auto - Updated documentation in README.md and README.zh-CN.md for clarity and completeness. - Revised references/requirement-plan.md with new details or planning criteria. - Removed obsolete skill-card","codeSnippets":[],"executableExamples":[],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: openapi-docs-generator\ndescription: >-\n  Help users with Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.. Use when a user asks for software-and-data, openapi, swagger, api documentation, rest api, or needs a practical workflow, artifact, checklist, analysis, or implementation support for this requirement.\n---\n\n# Openapi Docs Generator\n\n## Requirement\n\nUse this skill to help API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers with:\n\n> Validated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nDemand score: 100/100 (`70/70` demand, `30/30` local feasibility).\nEvidence: 12 signals across 4 source families.\n\nRead `references/requirement-plan.md` when source evidence, planning details, or review criteria are needed.\n\n## Workflow\n\n1. Restate the user's outcome, constraints, available inputs, and success criteria.\n2. Inspect technical constraints, propose implementation steps, and include test or verification commands when code or data is involved.\n3. Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.\n4. Keep the implementation local-hardware friendly: prefer scripts, templates, checklists, and small-model or CPU-safe workflows over cloud-only or large-training approaches.\n5. Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.\n6. Validate the output against the success criteria and list any remaining risks or follow-up work.\n\n## Expected Outputs\n\n- A tailored answer or artifact for the user's immediate situation.\n- A reusable checklist or workflow when the task is repeatable.\n- A verification note showing how the result was checked.\n\n## Validation\n\n- The output directly addresses the discovered requirement.\n- The user can act on the result without reading the original source post.\n- Assumptions, limits, and required inputs are visible.\n- The final response includes a short usage or next-step note when helpful.\n\n## Triggers\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nExample trigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use"},{"path":"README.md","content":"# Openapi Docs Generator\n\n## Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\nAudience: API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\nCategory: `software-and-data`\n\nDemand score: 100/100\n\nEvidence coverage: 12 signals across 4 source families.\n\n## Evidence\n\n- csdn-search: [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=461466c6d53a45ea9c6ee05f55500679&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base7&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues: [Shared artist knowledge API tools for interviewers and other agents](https://github.com/xdjs/MusicNerdWeb/issues/1424)\n- segmentfault-search: [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search: [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search: [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search: [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search: [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search: [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search: [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues: [Web Ask About, discovery review, and interviewer evaluation/integration](https://github.com/xdjs/MusicNerdWeb/issues/1422)\n- hacker-news-search: [You said no MCP](https://news.ycombinator.com/item?id=49908820)\n- hacker-news-search: [You said no MCP](https://news.ycombinator.com/item?id=49913269)\n\n## How This Skill Meets The Requirement\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## Usage\n\nKeywords: `software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\nTrigger sentences:\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle"},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7be2ewez5ks45t5nmdez8j51839xpk\",\n  \"slug\": \"openapi-docs-generator\",\n  \"version\": \"0.0.0-20261009-045810\",\n  \"publishedAt\": 1791522088148\n}"},{"path":"references/requirement-plan.md","content":"# Requirement Plan\n\n## Live Requirement\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n## Audience\n\nAPI developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n## Category\n\nsoftware-and-data\n\n## Requirement Score\n\nTotal: 100/100\n\nDemand: 70/70\n\nLocal feasibility: 30/30\n\nEvidence coverage: 12 signals across 4 source families.\n\nScoring rationale:\n\n- Evidence count: 12; required minimum: 3.\n- Distinct source families: 4; sources: csdn, github, hacker-news, segmentfault.\n- Demand score: 70/70 based on corroboration, source diversity, and professional/community signal.\n- Local feasibility score: 30/30.\n- Implementation is a documentation, workflow, code, or analysis skill that can run on ordinary CPU hardware.\n\n## Evidence\n\n- csdn-search (2026-03-13T00:00:00+00:00): [OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=461466c6d53a45ea9c6ee05f55500679&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base7&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues (2026-10-05T15:59:08+00:00): [Shared artist knowledge API tools for interviewers and other agents](https://github.com/xdjs/MusicNerdWeb/issues/1424)\n- segmentfault-search (2026-10-09T04:58:37.582837+00:00): [HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search (2026-10-09T04:58:37.582837+00:00): [javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search (2026-10-09T04:58:37.582837+00:00): [typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search (2026-10-09T04:58:37.582837+00:00): [ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search (2026-10-09T04:58:37.583376+00:00): [答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search (2026-10-09T04:58:37.583376+00:00): [OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search (2026-10-09T04:58:37.583376+00:00): [答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues (2026-10-04T15:40:39+00:00): [Web Ask About, discovery review, and interviewer evaluation/integration](https://github.com/xdjs/MusicNerdWeb/issues/1422)\n- hacker-news-search (2026-09-30T13:40:52+00:00): [You said no MCP](https://news.ycombinator.com/item?id=49908820)\n- hacker-news-search (2026-09-30T19"},{"path":"README.zh-CN.md","content":"# Openapi Docs Generator\n\n## 需求\n\nValidated demand: Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation for REST APIs. This requirement is supported by 12 separate online signals across 4 source families, so it represents broader demand rather than a single isolated request.\n\n目标用户：API developers, backend teams, developer-experience teams, and maintainers who must make services understandable to other engineers\n\n分类：`软件与数据`\n\n需求评分：100/100\n\n证据覆盖：12 条信号，覆盖 4 个来源类型。\n\n## 来源证据\n\n- csdn-search：[OpenAPI 规范：RESTful API设计](https://blog.csdn.net/2501_94476825/article/details/159013081?ops_request_misc=elastic_search_misc&request_id=461466c6d53a45ea9c6ee05f55500679&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~sobaiduend~default-5-159013081-null-null.142^v102^pc_search_result_base7&utm_term=OpenAPI%20%E6%96%87%E6%A1%A3)\n- github-issues：[Shared artist knowledge API tools for interviewers and other agents](https://github.com/xdjs/MusicNerdWeb/issues/1424)\n- segmentfault-search：[HarmonyOS 开发者社区](https://segmentfault.com/brand/harmonyos-next)\n- segmentfault-search：[javascript](https://segmentfault.com/t/javascript)\n- segmentfault-search：[typescript](https://segmentfault.com/t/typescript)\n- segmentfault-search：[ONES 研发管理](https://ones.cn/?utm_term=ONES%C2%A0%E7%A0%94%E5%8F%91%E7%AE%A1%E7%90%86&utm_campaign=%E9%A6%96%E9%A1%B5%E6%A0%87%E7%AD%BE&_channel_track_key=myqX1C0f&utm_source=%E6%80%9D%E5%90%A6%E8%BD%AC%20ONES)\n- segmentfault-search：[答： swagger发请求的时候如何自动添加Bearer](https://segmentfault.com/q/1010000017381307/a-1020000017382712)\n- segmentfault-search：[OpenAPI接口规范：为你的应用程序带来更好的性能与可维护性](https://segmentfault.com/a/1190000043968971)\n- segmentfault-search：[答： 如何为 swagger 2.8.0 做友好的基本 url](https://segmentfault.com/q/1010000042921070/a-1020000042921072)\n- github-issues：[Web Ask About, discovery review, and interviewer evaluation/integration](https://github.com/xdjs/MusicNerdWeb/issues/1422)\n- hacker-news-search：[You said no MCP](https://news.ycombinator.com/item?id=49908820)\n- hacker-news-search：[You said no MCP](https://news.ycombinator.com/item?id=49913269)\n\n## 这个技能如何满足需求\n\nTransforms the live request into a repeatable workflow that clarifies the user's context, produces a concrete deliverable, checks the result against the original need, and keeps execution feasible on ordinary CPU or family GPU hardware.\n\n## 使用方式\n\n关键词：`software-and-data`, `openapi`, `swagger`, `api documentation`, `rest api`, `developer experience`\n\n触发句：\n\n- `Help me Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `I need a practical workflow for Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n- `Use $openapi-docs-generator to handle Backend and platform teams need practical help generating, improving, and validating OpenAPI or Swagger documentation fo.`\n\n## 文件\n\n- `SK"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1871,"uniquenessScore":32,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T11:09:31.605Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T11:09:31.605Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T16:07:19.323Z","emptyReason":null},"items":[{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-10T18:48:31.762Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}