{
  "schemaVersion": "1.0",
  "item": {
    "slug": "codebase-documenter",
    "name": "Codebase Documenter",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/Veeramanikandanr48/codebase-documenter",
    "canonicalUrl": "https://clawhub.ai/Veeramanikandanr48/codebase-documenter",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/codebase-documenter",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=codebase-documenter",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "assets/templates/API.template.md",
      "assets/templates/ARCHITECTURE.template.md",
      "assets/templates/CODE_COMMENTS.template.md",
      "assets/templates/README.template.md",
      "index.js"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/codebase-documenter"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/codebase-documenter",
    "agentPageUrl": "https://openagent3.xyz/skills/codebase-documenter/agent",
    "manifestUrl": "https://openagent3.xyz/skills/codebase-documenter/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/codebase-documenter/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Overview",
        "body": "This skill enables creating comprehensive, beginner-friendly documentation for codebases. It provides structured templates and best practices for writing READMEs, architecture guides, code comments, and API documentation that help new users quickly understand and contribute to projects."
      },
      {
        "title": "Core Principles for Beginner-Friendly Documentation",
        "body": "When documenting code for new users, follow these fundamental principles:\n\nStart with the \"Why\" - Explain the purpose before diving into implementation details\nUse Progressive Disclosure - Present information in layers from simple to complex\nProvide Context - Explain not just what the code does, but why it exists\nInclude Examples - Show concrete usage examples for every concept\nAssume No Prior Knowledge - Define terms and avoid jargon when possible\nVisual Aids - Use diagrams, flowcharts, and file tree structures\nQuick Wins - Help users get something running within 5 minutes"
      },
      {
        "title": "1. README Documentation",
        "body": "When to create: For project root directories, major feature modules, or standalone components.\n\nStructure to follow:\n\n# Project Name\n\n## What This Does\n[1-2 sentence plain-English explanation]\n\n## Quick Start\n[Get users running the project in < 5 minutes]\n\n## Project Structure\n[Visual file tree with explanations]\n\n## Key Concepts\n[Core concepts users need to understand]\n\n## Common Tasks\n[Step-by-step guides for frequent operations]\n\n## Troubleshooting\n[Common issues and solutions]\n\nBest practices:\n\nLead with the project's value proposition\nInclude setup instructions that actually work (test them!)\nProvide a visual overview of the project structure\nLink to deeper documentation for advanced topics\nKeep the root README focused on getting started"
      },
      {
        "title": "2. Architecture Documentation",
        "body": "When to create: For projects with multiple modules, complex data flows, or non-obvious design decisions.\n\nStructure to follow:\n\n# Architecture Overview\n\n## System Design\n[High-level diagram and explanation]\n\n## Directory Structure\n[Detailed breakdown with purpose of each directory]\n\n## Data Flow\n[How data moves through the system]\n\n## Key Design Decisions\n[Why certain architectural choices were made]\n\n## Module Dependencies\n[How different parts interact]\n\n## Extension Points\n[Where and how to add new features]\n\nBest practices:\n\nUse diagrams to show system components and relationships\nExplain the \"why\" behind architectural decisions\nDocument both the happy path and error handling\nIdentify boundaries between modules\nInclude visual file tree structures with annotations"
      },
      {
        "title": "3. Code Comments",
        "body": "When to create: For complex logic, non-obvious algorithms, or code that requires context.\n\nAnnotation patterns:\n\nFunction/Method Documentation:\n\n/**\n * Calculates the prorated subscription cost for a partial billing period.\n *\n * Why this exists: Users can subscribe mid-month, so we need to charge\n * them only for the days remaining in the current billing cycle.\n *\n * @param {number} fullPrice - The normal monthly subscription price\n * @param {Date} startDate - When the user's subscription begins\n * @param {Date} periodEnd - End of the current billing period\n * @returns {number} The prorated amount to charge\n *\n * @example\n * // User subscribes on Jan 15, period ends Jan 31\n * calculateProratedCost(30, new Date('2024-01-15'), new Date('2024-01-31'))\n * // Returns: 16.13 (17 days out of 31 days)\n */\n\nComplex Logic Documentation:\n\n# Why this check exists: The API returns null for deleted users,\n# but empty string for users who never set a name. We need to\n# distinguish between these cases for the audit log.\nif user_name is None:\n    # User was deleted - log this as a security event\n    log_deletion_event(user_id)\nelif user_name == \"\":\n    # User never completed onboarding - safe to skip\n    continue\n\nBest practices:\n\nExplain \"why\" not \"what\" - the code shows what it does\nDocument edge cases and business logic\nAdd examples for complex functions\nExplain parameters that aren't self-explanatory\nNote any gotchas or counterintuitive behavior"
      },
      {
        "title": "4. API Documentation",
        "body": "When to create: For any HTTP endpoints, SDK methods, or public interfaces.\n\nStructure to follow:\n\n## Endpoint Name\n\n### What It Does\n[Plain-English explanation of the endpoint's purpose]\n\n### Endpoint\n`POST /api/v1/resource`\n\n### Authentication\n[What auth is required and how to provide it]\n\n### Request Format\n[JSON schema or example request]\n\n### Response Format\n[JSON schema or example response]\n\n### Example Usage\n[Concrete example with curl/code]\n\n### Common Errors\n[Error codes and what they mean]\n\n### Related Endpoints\n[Links to related operations]\n\nBest practices:\n\nProvide working curl examples\nShow both success and error responses\nExplain authentication clearly\nDocument rate limits and constraints\nInclude troubleshooting for common issues"
      },
      {
        "title": "Step 1: Analyze the Codebase",
        "body": "Before writing documentation:\n\nIdentify entry points - Main files, index files, app initialization\nMap dependencies - How modules relate to each other\nFind core concepts - Key abstractions users need to understand\nLocate configuration - Environment setup, config files\nReview existing docs - Build on what's there, don't duplicate"
      },
      {
        "title": "Step 2: Choose Documentation Type",
        "body": "Based on user request and codebase analysis:\n\nNew project or missing README → Start with README documentation\nComplex architecture or multiple modules → Create architecture documentation\nConfusing code sections → Add inline code comments\nHTTP/API endpoints → Write API documentation\nMultiple types needed → Address in order: README → Architecture → API → Comments"
      },
      {
        "title": "Step 3: Generate Documentation",
        "body": "Use the templates from assets/templates/ as starting points:\n\nassets/templates/README.template.md - For project READMEs\nassets/templates/ARCHITECTURE.template.md - For architecture docs\nassets/templates/API.template.md - For API documentation\n\nCustomize templates based on the specific codebase:\n\nFill in project-specific information - Replace placeholders with actual content\nAdd concrete examples - Use real code from the project\nInclude visual aids - Create file trees, diagrams, flowcharts\nTest instructions - Verify setup steps actually work\nLink related docs - Connect documentation pieces together"
      },
      {
        "title": "Step 4: Review for Clarity",
        "body": "Before finalizing documentation:\n\nRead as a beginner - Does it make sense without project context?\nCheck completeness - Are there gaps in the explanation?\nVerify examples - Do code examples actually work?\nTest instructions - Can someone follow the setup steps?\nImprove structure - Is information easy to find?"
      },
      {
        "title": "Documentation Templates",
        "body": "This skill includes several templates in assets/templates/ that provide starting structures:"
      },
      {
        "title": "Available Templates",
        "body": "README.template.md - Comprehensive README structure with sections for quick start, project structure, and common tasks\nARCHITECTURE.template.md - Architecture documentation template with system design, data flow, and design decisions\nAPI.template.md - API endpoint documentation with request/response formats and examples\nCODE_COMMENTS.template.md - Examples and patterns for effective inline documentation"
      },
      {
        "title": "Using Templates",
        "body": "Read the appropriate template from assets/templates/\nCustomize for the specific project - Replace placeholders with actual information\nAdd project-specific sections - Extend the template as needed\nInclude real examples - Use actual code from the codebase\nRemove irrelevant sections - Delete parts that don't apply"
      },
      {
        "title": "Best Practices Reference",
        "body": "For detailed documentation best practices, style guidelines, and advanced patterns, refer to:\n\nreferences/documentation_guidelines.md - Comprehensive style guide and best practices\nreferences/visual_aids_guide.md - How to create effective diagrams and file trees\n\nLoad these references when:\n\nCreating documentation for complex enterprise codebases\nDealing with multiple stakeholder requirements\nNeeding advanced documentation patterns\nStandardizing documentation across a large project"
      },
      {
        "title": "Creating File Tree Structures",
        "body": "File trees help new users understand project organization:\n\nproject-root/\n├── src/                    # Source code\n│   ├── components/        # Reusable UI components\n│   ├── pages/             # Page-level components (routing)\n│   ├── services/          # Business logic and API calls\n│   ├── utils/             # Helper functions\n│   └── types/             # TypeScript type definitions\n├── public/                # Static assets (images, fonts)\n├── tests/                 # Test files mirroring src structure\n└── package.json           # Dependencies and scripts"
      },
      {
        "title": "Explaining Complex Data Flows",
        "body": "Use numbered steps with diagrams:\n\nUser Request Flow:\n1. User submits form → 2. Validation → 3. API call → 4. Database → 5. Response\n\n[1] components/UserForm.tsx\n    ↓ validates input\n[2] services/validation.ts\n    ↓ sends to API\n[3] services/api.ts\n    ↓ queries database\n[4] Database (PostgreSQL)\n    ↓ returns data\n[5] components/UserForm.tsx (updates UI)"
      },
      {
        "title": "Documenting Design Decisions",
        "body": "Capture the \"why\" behind architectural choices:\n\n## Why We Use Redux\n\n**Decision:** State management with Redux instead of Context API\n\n**Context:** Our app has 50+ components that need access to user\nauthentication state, shopping cart, and UI preferences.\n\n**Reasoning:**\n- Context API causes unnecessary re-renders with this many components\n- Redux DevTools helps debug complex state changes\n- Team has existing Redux expertise\n\n**Trade-offs:**\n- More boilerplate code\n- Steeper learning curve for new developers\n- Worth it for: performance, debugging, team familiarity"
      },
      {
        "title": "Output Guidelines",
        "body": "When generating documentation:\n\nWrite for the target audience - Adjust complexity based on whether documentation is for beginners, intermediate, or advanced users\nUse consistent formatting - Follow markdown conventions, consistent heading hierarchy\nProvide working examples - Test all code snippets and commands\nLink between documents - Create a documentation navigation structure\nKeep it maintainable - Documentation should be easy to update as code changes\nAdd dates and versions - Note when documentation was last updated"
      },
      {
        "title": "Quick Reference",
        "body": "Command to generate README:\n\"Create a README file for this project that helps new developers get started\"\n\nCommand to document architecture:\n\"Document the architecture of this codebase, explaining how the different modules interact\"\n\nCommand to add code comments:\n\"Add explanatory comments to this file that help new developers understand the logic\"\n\nCommand to document API:\n\"Create API documentation for all the endpoints in this file\""
      }
    ],
    "body": "Codebase Documenter\nOverview\n\nThis skill enables creating comprehensive, beginner-friendly documentation for codebases. It provides structured templates and best practices for writing READMEs, architecture guides, code comments, and API documentation that help new users quickly understand and contribute to projects.\n\nCore Principles for Beginner-Friendly Documentation\n\nWhen documenting code for new users, follow these fundamental principles:\n\nStart with the \"Why\" - Explain the purpose before diving into implementation details\nUse Progressive Disclosure - Present information in layers from simple to complex\nProvide Context - Explain not just what the code does, but why it exists\nInclude Examples - Show concrete usage examples for every concept\nAssume No Prior Knowledge - Define terms and avoid jargon when possible\nVisual Aids - Use diagrams, flowcharts, and file tree structures\nQuick Wins - Help users get something running within 5 minutes\nDocumentation Types and When to Use Them\n1. README Documentation\n\nWhen to create: For project root directories, major feature modules, or standalone components.\n\nStructure to follow:\n\n# Project Name\n\n## What This Does\n[1-2 sentence plain-English explanation]\n\n## Quick Start\n[Get users running the project in < 5 minutes]\n\n## Project Structure\n[Visual file tree with explanations]\n\n## Key Concepts\n[Core concepts users need to understand]\n\n## Common Tasks\n[Step-by-step guides for frequent operations]\n\n## Troubleshooting\n[Common issues and solutions]\n\n\nBest practices:\n\nLead with the project's value proposition\nInclude setup instructions that actually work (test them!)\nProvide a visual overview of the project structure\nLink to deeper documentation for advanced topics\nKeep the root README focused on getting started\n2. Architecture Documentation\n\nWhen to create: For projects with multiple modules, complex data flows, or non-obvious design decisions.\n\nStructure to follow:\n\n# Architecture Overview\n\n## System Design\n[High-level diagram and explanation]\n\n## Directory Structure\n[Detailed breakdown with purpose of each directory]\n\n## Data Flow\n[How data moves through the system]\n\n## Key Design Decisions\n[Why certain architectural choices were made]\n\n## Module Dependencies\n[How different parts interact]\n\n## Extension Points\n[Where and how to add new features]\n\n\nBest practices:\n\nUse diagrams to show system components and relationships\nExplain the \"why\" behind architectural decisions\nDocument both the happy path and error handling\nIdentify boundaries between modules\nInclude visual file tree structures with annotations\n3. Code Comments\n\nWhen to create: For complex logic, non-obvious algorithms, or code that requires context.\n\nAnnotation patterns:\n\nFunction/Method Documentation:\n\n/**\n * Calculates the prorated subscription cost for a partial billing period.\n *\n * Why this exists: Users can subscribe mid-month, so we need to charge\n * them only for the days remaining in the current billing cycle.\n *\n * @param {number} fullPrice - The normal monthly subscription price\n * @param {Date} startDate - When the user's subscription begins\n * @param {Date} periodEnd - End of the current billing period\n * @returns {number} The prorated amount to charge\n *\n * @example\n * // User subscribes on Jan 15, period ends Jan 31\n * calculateProratedCost(30, new Date('2024-01-15'), new Date('2024-01-31'))\n * // Returns: 16.13 (17 days out of 31 days)\n */\n\n\nComplex Logic Documentation:\n\n# Why this check exists: The API returns null for deleted users,\n# but empty string for users who never set a name. We need to\n# distinguish between these cases for the audit log.\nif user_name is None:\n    # User was deleted - log this as a security event\n    log_deletion_event(user_id)\nelif user_name == \"\":\n    # User never completed onboarding - safe to skip\n    continue\n\n\nBest practices:\n\nExplain \"why\" not \"what\" - the code shows what it does\nDocument edge cases and business logic\nAdd examples for complex functions\nExplain parameters that aren't self-explanatory\nNote any gotchas or counterintuitive behavior\n4. API Documentation\n\nWhen to create: For any HTTP endpoints, SDK methods, or public interfaces.\n\nStructure to follow:\n\n## Endpoint Name\n\n### What It Does\n[Plain-English explanation of the endpoint's purpose]\n\n### Endpoint\n`POST /api/v1/resource`\n\n### Authentication\n[What auth is required and how to provide it]\n\n### Request Format\n[JSON schema or example request]\n\n### Response Format\n[JSON schema or example response]\n\n### Example Usage\n[Concrete example with curl/code]\n\n### Common Errors\n[Error codes and what they mean]\n\n### Related Endpoints\n[Links to related operations]\n\n\nBest practices:\n\nProvide working curl examples\nShow both success and error responses\nExplain authentication clearly\nDocument rate limits and constraints\nInclude troubleshooting for common issues\nDocumentation Workflow\nStep 1: Analyze the Codebase\n\nBefore writing documentation:\n\nIdentify entry points - Main files, index files, app initialization\nMap dependencies - How modules relate to each other\nFind core concepts - Key abstractions users need to understand\nLocate configuration - Environment setup, config files\nReview existing docs - Build on what's there, don't duplicate\nStep 2: Choose Documentation Type\n\nBased on user request and codebase analysis:\n\nNew project or missing README → Start with README documentation\nComplex architecture or multiple modules → Create architecture documentation\nConfusing code sections → Add inline code comments\nHTTP/API endpoints → Write API documentation\nMultiple types needed → Address in order: README → Architecture → API → Comments\nStep 3: Generate Documentation\n\nUse the templates from assets/templates/ as starting points:\n\nassets/templates/README.template.md - For project READMEs\nassets/templates/ARCHITECTURE.template.md - For architecture docs\nassets/templates/API.template.md - For API documentation\n\nCustomize templates based on the specific codebase:\n\nFill in project-specific information - Replace placeholders with actual content\nAdd concrete examples - Use real code from the project\nInclude visual aids - Create file trees, diagrams, flowcharts\nTest instructions - Verify setup steps actually work\nLink related docs - Connect documentation pieces together\nStep 4: Review for Clarity\n\nBefore finalizing documentation:\n\nRead as a beginner - Does it make sense without project context?\nCheck completeness - Are there gaps in the explanation?\nVerify examples - Do code examples actually work?\nTest instructions - Can someone follow the setup steps?\nImprove structure - Is information easy to find?\nDocumentation Templates\n\nThis skill includes several templates in assets/templates/ that provide starting structures:\n\nAvailable Templates\nREADME.template.md - Comprehensive README structure with sections for quick start, project structure, and common tasks\nARCHITECTURE.template.md - Architecture documentation template with system design, data flow, and design decisions\nAPI.template.md - API endpoint documentation with request/response formats and examples\nCODE_COMMENTS.template.md - Examples and patterns for effective inline documentation\nUsing Templates\nRead the appropriate template from assets/templates/\nCustomize for the specific project - Replace placeholders with actual information\nAdd project-specific sections - Extend the template as needed\nInclude real examples - Use actual code from the codebase\nRemove irrelevant sections - Delete parts that don't apply\nBest Practices Reference\n\nFor detailed documentation best practices, style guidelines, and advanced patterns, refer to:\n\nreferences/documentation_guidelines.md - Comprehensive style guide and best practices\nreferences/visual_aids_guide.md - How to create effective diagrams and file trees\n\nLoad these references when:\n\nCreating documentation for complex enterprise codebases\nDealing with multiple stakeholder requirements\nNeeding advanced documentation patterns\nStandardizing documentation across a large project\nCommon Patterns\nCreating File Tree Structures\n\nFile trees help new users understand project organization:\n\nproject-root/\n├── src/                    # Source code\n│   ├── components/        # Reusable UI components\n│   ├── pages/             # Page-level components (routing)\n│   ├── services/          # Business logic and API calls\n│   ├── utils/             # Helper functions\n│   └── types/             # TypeScript type definitions\n├── public/                # Static assets (images, fonts)\n├── tests/                 # Test files mirroring src structure\n└── package.json           # Dependencies and scripts\n\nExplaining Complex Data Flows\n\nUse numbered steps with diagrams:\n\nUser Request Flow:\n1. User submits form → 2. Validation → 3. API call → 4. Database → 5. Response\n\n[1] components/UserForm.tsx\n    ↓ validates input\n[2] services/validation.ts\n    ↓ sends to API\n[3] services/api.ts\n    ↓ queries database\n[4] Database (PostgreSQL)\n    ↓ returns data\n[5] components/UserForm.tsx (updates UI)\n\nDocumenting Design Decisions\n\nCapture the \"why\" behind architectural choices:\n\n## Why We Use Redux\n\n**Decision:** State management with Redux instead of Context API\n\n**Context:** Our app has 50+ components that need access to user\nauthentication state, shopping cart, and UI preferences.\n\n**Reasoning:**\n- Context API causes unnecessary re-renders with this many components\n- Redux DevTools helps debug complex state changes\n- Team has existing Redux expertise\n\n**Trade-offs:**\n- More boilerplate code\n- Steeper learning curve for new developers\n- Worth it for: performance, debugging, team familiarity\n\nOutput Guidelines\n\nWhen generating documentation:\n\nWrite for the target audience - Adjust complexity based on whether documentation is for beginners, intermediate, or advanced users\nUse consistent formatting - Follow markdown conventions, consistent heading hierarchy\nProvide working examples - Test all code snippets and commands\nLink between documents - Create a documentation navigation structure\nKeep it maintainable - Documentation should be easy to update as code changes\nAdd dates and versions - Note when documentation was last updated\nQuick Reference\n\nCommand to generate README: \"Create a README file for this project that helps new developers get started\"\n\nCommand to document architecture: \"Document the architecture of this codebase, explaining how the different modules interact\"\n\nCommand to add code comments: \"Add explanatory comments to this file that help new developers understand the logic\"\n\nCommand to document API: \"Create API documentation for all the endpoints in this file\""
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/Veeramanikandanr48/codebase-documenter",
    "publisherUrl": "https://clawhub.ai/Veeramanikandanr48/codebase-documenter",
    "owner": "Veeramanikandanr48",
    "version": "0.1.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/codebase-documenter",
    "downloadUrl": "https://openagent3.xyz/downloads/codebase-documenter",
    "agentUrl": "https://openagent3.xyz/skills/codebase-documenter/agent",
    "manifestUrl": "https://openagent3.xyz/skills/codebase-documenter/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/codebase-documenter/agent.md"
  }
}