{
  "schemaVersion": "1.0",
  "item": {
    "slug": "style-guide-generator",
    "name": "Style Guide Generator",
    "source": "tencent",
    "type": "skill",
    "category": "内容创作",
    "sourceUrl": "https://clawhub.ai/TomsTools11/style-guide-generator",
    "canonicalUrl": "https://clawhub.ai/TomsTools11/style-guide-generator",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/style-guide-generator",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=style-guide-generator",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "design_system_examples.md",
      "SKILL.md"
    ],
    "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/style-guide-generator"
    },
    "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/style-guide-generator",
    "agentPageUrl": "https://openagent3.xyz/skills/style-guide-generator/agent",
    "manifestUrl": "https://openagent3.xyz/skills/style-guide-generator/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/style-guide-generator/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": "Generate professionally formatted website style guides and design systems by analyzing provided URLs, screenshots, uploaded files, and user requirements. Output comprehensive PDF documents that serve as the single source of truth for design and development teams."
      },
      {
        "title": "Workflow Decision Tree",
        "body": "When a user requests a style guide, follow this decision tree:\n\nGather Information\n\nIf user provides URL → Use web_fetch to analyze the website\nIf user provides screenshots/images → Analyze visual elements\nIf user provides existing documentation → Extract and structure information\nIf user provides minimal information → Ask clarifying questions about brand, goals, and requirements\n\n\n\nExtract Design Elements\n\nColors (primary, secondary, accent, text, background, success, warning, error)\nTypography (fonts, weights, sizes, line heights)\nLogo usage guidelines\nIconography style\nImagery preferences\nUI component patterns\nLayout and spacing systems\nAccessibility requirements\n\n\n\nStructure Content\n\nFollow the standard template structure (see Template Structure section)\nOrganize extracted information into appropriate sections\nAdd mission/vision if provided or inferred\nDocument design principles\nCreate component specifications\n\n\n\nGenerate PDF\n\nUse the PDF skill to create a professional document\nApply consistent formatting and typography\nInclude tables for color palettes, typography specs, and component states\nEnsure accessibility with proper contrast ratios\nAdd version number and last updated date"
      },
      {
        "title": "Standard Template Structure",
        "body": "Every style guide should follow this professional structure (based on industry best practices):"
      },
      {
        "title": "1.0 Introduction",
        "body": "Version number and last updated date\nPurpose and scope statement\nTarget audience (design and development teams)"
      },
      {
        "title": "1.1 Mission & Vision",
        "body": "Company mission statement\nCompany vision statement\nStrategic positioning"
      },
      {
        "title": "1.2 Design Principles",
        "body": "4-6 core principles that guide design decisions\nEach principle with name and description\nExamples: \"Clarity Above All\", \"Empowerment Through Simplicity\", \"Consistency Builds Trust\", \"Human-Centered\""
      },
      {
        "title": "2.0 Brand Identity",
        "body": "2.1 Logo Usage\n\nPrimary logo specifications\nClear space requirements\nIncorrect usage examples\nMinimum size requirements\nColor variations (full color, black, white)\n\n2.2 Color Palette\n\nOrganized table with Role, Color Name, HEX, and RGB values\nPrimary colors (1-2)\nSecondary colors (1-3)\nAccent colors\nText colors\nBackground colors\nSystem colors (Success, Warning, Error)\nAccessibility notes for each color combination\n\n2.3 Typography\n\nHeading font specifications (H1, H2, H3)\nBody text specifications\nCaption/small text specifications\nFont families, weights, sizes, and line heights in tabular format\nWeb font loading considerations\nFallback fonts\n\n2.4 Iconography\n\nIcon style guidelines (outlined, filled, line weight)\nGrid system specifications\nSize variants\nUsage examples\nLink to icon library\n\n2.5 Imagery\n\nPhotography style guidelines\nIllustration style guidelines\nImage treatment specifications\nDo's and don'ts\nQuality requirements"
      },
      {
        "title": "3.0 Content Style Guide",
        "body": "3.1 Voice and Tone\n\nVoice characteristics (consistent attributes)\nTone variations (how voice adapts to context)\nExamples for different scenarios\n\n3.2 Grammar and Mechanics\n\nPunctuation rules\nCapitalization standards\nVoice preference (active/passive)\nNumber formatting\nDate and time formatting"
      },
      {
        "title": "4.0 UI Components",
        "body": "4.1 Buttons\n\nState variants (Primary, Secondary, Tertiary, Disabled)\nSize variants\nUsage guidelines\nCode snippets (HTML/CSS)\nAccessibility requirements\n\n4.2 Forms\n\nInput field specifications\nLabel positioning\nValidation states\nRequired field indicators\nError message styling\nHelp text formatting\n\n4.3 [Additional Components as needed]\n\nCards\nModals\nNavigation\nTables\nAlerts/Notifications\nTooltips\nBadges\nProgress indicators"
      },
      {
        "title": "5.0 Layout & Grid",
        "body": "Grid system specifications (columns, gutters)\nResponsive breakpoints\nSpacing scale (base unit and multipliers)\nContainer widths\nMargin and padding conventions"
      },
      {
        "title": "6.0 Accessibility (A11y)",
        "body": "WCAG compliance level (2.1 AA standard)\nColor contrast requirements\nAlt text guidelines\nKeyboard navigation standards\nScreen reader considerations\nFocus indicators"
      },
      {
        "title": "7.0 Resources",
        "body": "Links to design files (Figma, Sketch, Adobe XD)\nIcon library location\nIllustration library location\nFont files repository\nCode repository\nAdditional documentation"
      },
      {
        "title": "8.0 Changelog",
        "body": "Version history with dates\nChanges summary for each version"
      },
      {
        "title": "Information Extraction Process",
        "body": "When analyzing provided materials, extract the following systematically:"
      },
      {
        "title": "From URLs/Websites:",
        "body": "Fetch the website using web_fetch\nAnalyze HTML/CSS for:\n\nColor values (background-color, color properties)\nFont families and typography (font-family, font-size, font-weight)\nSpacing patterns (margin, padding values)\nComponent structures\n\n\nTake note of:\n\nVisual hierarchy\nButton styles and states\nForm element treatments\nNavigation patterns\nResponsive behavior (if observable)"
      },
      {
        "title": "From Screenshots/Images:",
        "body": "Identify color palette using visual analysis\nDetermine typography hierarchy\nNote spacing and layout patterns\nIdentify UI component variants\nObserve design principles in practice"
      },
      {
        "title": "From Existing Documentation:",
        "body": "Extract mission/vision statements\nGather existing brand guidelines\nCollect color specifications\nDocument current typography standards\nNote any existing component libraries"
      },
      {
        "title": "Creating Professional Tables",
        "body": "Use well-formatted tables for specifications. Example formats:\n\nColor Palette Table:\n\n| Role       | Color       | HEX     | RGB           |\n|------------|-------------|---------|---------------|\n| Primary    | Brand Blue  | #378DFF | 55, 141, 255  |\n| Secondary  | Light Blue  | #A5CAFF | 165, 202, 255 |\n\nTypography Table:\n\n| Element | Font Family | Weight  | Size (px) | Line Height |\n|---------|-------------|---------|-----------|-------------|\n| H1      | Inter       | Bold    | 48        | 1.2         |\n| H2      | Inter       | Bold    | 36        | 1.3         |\n| Body    | Inter       | Regular | 16        | 1.5         |\n\nButton States Table:\n\n| State     | Appearance              | Usage                          |\n|-----------|-------------------------|--------------------------------|\n| Primary   | Solid fill, primary     | Main call to action on a page  |\n| Secondary | Outline, primary color  | Secondary actions              |\n| Tertiary  | Text only              | Less important actions         |"
      },
      {
        "title": "PDF Generation Best Practices",
        "body": "Professional Formatting:\n\nUse consistent heading hierarchy\nApply proper spacing between sections\nUtilize tables for structured data\nInclude visual examples where possible\n\n\n\nTypography:\n\nUse professional fonts (Inter, Roboto, or system fonts)\nMaintain consistent sizing hierarchy\nEnsure sufficient line height for readability\n\n\n\nColor Usage:\n\nShow color swatches with hex codes\nEnsure sufficient contrast for accessibility\nDocument color roles clearly\n\n\n\nOrganization:\n\nNumber sections clearly (1.0, 1.1, 2.0, etc.)\nInclude table of contents for longer guides\nUse page breaks appropriately\nAdd page numbers\n\n\n\nAccessibility:\n\nEnsure document is screen-reader friendly\nUse proper heading structure\nInclude alt text for images\nMaintain minimum font size of 12pt"
      },
      {
        "title": "Handling Incomplete Information",
        "body": "When information is missing or unclear:\n\nMake Reasonable Inferences:\n\nExtract colors from provided screenshots\nInfer typography from website analysis\nEstimate spacing based on visual patterns\n\n\n\nUse Placeholders:\n\n\"[Insert company mission statement]\" for unknown content\n\"[Link to design files]\" for unavailable resources\n\"Version 1.0\" and current date as defaults\n\n\n\nAsk Clarifying Questions:\n\n\"What is your company's mission statement?\"\n\"Do you have existing brand colors or should I extract them from the website?\"\n\"Are there specific accessibility requirements beyond WCAG 2.1 AA?\"\n\n\n\nProvide Templates:\n\nInclude example text for sections that need user input\nShow format for content they should provide\nGive guidance on what information would be ideal"
      },
      {
        "title": "Example User Interactions",
        "body": "Example 1: URL-Based Request\nUser: \"Create a style guide for my website at example.com\"\nProcess:\n\nFetch website with web_fetch\nAnalyze HTML/CSS for design system\nExtract colors, fonts, spacing\nStructure into standard template\nGenerate professional PDF\nProvide download link\n\nExample 2: Screenshot-Based Request\nUser: \"Here are screenshots of my app. Create a style guide.\" [uploads images]\nProcess:\n\nAnalyze images for visual elements\nExtract color palette\nIdentify typography patterns\nDocument component styles\nFill in template structure\nGenerate PDF with findings\nProvide download link\n\nExample 3: Comprehensive Request\nUser: \"Create a style guide using my website URL, these brand colors [list], and our mission statement [text]\"\nProcess:\n\nCombine all provided information\nFetch and analyze website\nIntegrate provided brand elements\nStructure complete style guide\nGenerate professional PDF\nProvide download link"
      },
      {
        "title": "Quality Checklist",
        "body": "Before delivering the style guide PDF, verify:\n\nAll sections are complete or marked as placeholders\n Color palette includes HEX and RGB values\n Typography specifications are detailed (family, weight, size, line height)\n Tables are properly formatted and aligned\n Accessibility requirements are documented\n Version number and date are included\n Resources section links are provided (even if placeholder)\n Changelog is started with version 1.0\n PDF is professionally formatted\n Document is ready for team distribution"
      },
      {
        "title": "Resources",
        "body": "This skill uses the following bundled resources:"
      },
      {
        "title": "assets/template.pdf",
        "body": "The base template PDF that demonstrates the professional structure and formatting that all generated style guides should follow. This file serves as a reference for structure, section organization, and formatting standards."
      },
      {
        "title": "scripts/analyze_website.py",
        "body": "Python script to extract design system information from websites, including colors, typography, and component patterns. Can be used to automatically gather design specifications from live URLs."
      },
      {
        "title": "references/design_system_examples.md",
        "body": "Reference document containing examples of well-structured design systems and style guides from leading companies. Use this for inspiration on content organization and presentation standards."
      }
    ],
    "body": "Style Guide Generator\nOverview\n\nGenerate professionally formatted website style guides and design systems by analyzing provided URLs, screenshots, uploaded files, and user requirements. Output comprehensive PDF documents that serve as the single source of truth for design and development teams.\n\nWorkflow Decision Tree\n\nWhen a user requests a style guide, follow this decision tree:\n\nGather Information\n\nIf user provides URL → Use web_fetch to analyze the website\nIf user provides screenshots/images → Analyze visual elements\nIf user provides existing documentation → Extract and structure information\nIf user provides minimal information → Ask clarifying questions about brand, goals, and requirements\n\nExtract Design Elements\n\nColors (primary, secondary, accent, text, background, success, warning, error)\nTypography (fonts, weights, sizes, line heights)\nLogo usage guidelines\nIconography style\nImagery preferences\nUI component patterns\nLayout and spacing systems\nAccessibility requirements\n\nStructure Content\n\nFollow the standard template structure (see Template Structure section)\nOrganize extracted information into appropriate sections\nAdd mission/vision if provided or inferred\nDocument design principles\nCreate component specifications\n\nGenerate PDF\n\nUse the PDF skill to create a professional document\nApply consistent formatting and typography\nInclude tables for color palettes, typography specs, and component states\nEnsure accessibility with proper contrast ratios\nAdd version number and last updated date\nStandard Template Structure\n\nEvery style guide should follow this professional structure (based on industry best practices):\n\n1.0 Introduction\nVersion number and last updated date\nPurpose and scope statement\nTarget audience (design and development teams)\n1.1 Mission & Vision\nCompany mission statement\nCompany vision statement\nStrategic positioning\n1.2 Design Principles\n4-6 core principles that guide design decisions\nEach principle with name and description\nExamples: \"Clarity Above All\", \"Empowerment Through Simplicity\", \"Consistency Builds Trust\", \"Human-Centered\"\n2.0 Brand Identity\n2.1 Logo Usage\nPrimary logo specifications\nClear space requirements\nIncorrect usage examples\nMinimum size requirements\nColor variations (full color, black, white)\n2.2 Color Palette\nOrganized table with Role, Color Name, HEX, and RGB values\nPrimary colors (1-2)\nSecondary colors (1-3)\nAccent colors\nText colors\nBackground colors\nSystem colors (Success, Warning, Error)\nAccessibility notes for each color combination\n2.3 Typography\nHeading font specifications (H1, H2, H3)\nBody text specifications\nCaption/small text specifications\nFont families, weights, sizes, and line heights in tabular format\nWeb font loading considerations\nFallback fonts\n2.4 Iconography\nIcon style guidelines (outlined, filled, line weight)\nGrid system specifications\nSize variants\nUsage examples\nLink to icon library\n2.5 Imagery\nPhotography style guidelines\nIllustration style guidelines\nImage treatment specifications\nDo's and don'ts\nQuality requirements\n3.0 Content Style Guide\n3.1 Voice and Tone\nVoice characteristics (consistent attributes)\nTone variations (how voice adapts to context)\nExamples for different scenarios\n3.2 Grammar and Mechanics\nPunctuation rules\nCapitalization standards\nVoice preference (active/passive)\nNumber formatting\nDate and time formatting\n4.0 UI Components\n4.1 Buttons\nState variants (Primary, Secondary, Tertiary, Disabled)\nSize variants\nUsage guidelines\nCode snippets (HTML/CSS)\nAccessibility requirements\n4.2 Forms\nInput field specifications\nLabel positioning\nValidation states\nRequired field indicators\nError message styling\nHelp text formatting\n4.3 [Additional Components as needed]\nCards\nModals\nNavigation\nTables\nAlerts/Notifications\nTooltips\nBadges\nProgress indicators\n5.0 Layout & Grid\nGrid system specifications (columns, gutters)\nResponsive breakpoints\nSpacing scale (base unit and multipliers)\nContainer widths\nMargin and padding conventions\n6.0 Accessibility (A11y)\nWCAG compliance level (2.1 AA standard)\nColor contrast requirements\nAlt text guidelines\nKeyboard navigation standards\nScreen reader considerations\nFocus indicators\n7.0 Resources\nLinks to design files (Figma, Sketch, Adobe XD)\nIcon library location\nIllustration library location\nFont files repository\nCode repository\nAdditional documentation\n8.0 Changelog\nVersion history with dates\nChanges summary for each version\nInformation Extraction Process\n\nWhen analyzing provided materials, extract the following systematically:\n\nFrom URLs/Websites:\nFetch the website using web_fetch\nAnalyze HTML/CSS for:\nColor values (background-color, color properties)\nFont families and typography (font-family, font-size, font-weight)\nSpacing patterns (margin, padding values)\nComponent structures\nTake note of:\nVisual hierarchy\nButton styles and states\nForm element treatments\nNavigation patterns\nResponsive behavior (if observable)\nFrom Screenshots/Images:\nIdentify color palette using visual analysis\nDetermine typography hierarchy\nNote spacing and layout patterns\nIdentify UI component variants\nObserve design principles in practice\nFrom Existing Documentation:\nExtract mission/vision statements\nGather existing brand guidelines\nCollect color specifications\nDocument current typography standards\nNote any existing component libraries\nCreating Professional Tables\n\nUse well-formatted tables for specifications. Example formats:\n\nColor Palette Table:\n\n| Role       | Color       | HEX     | RGB           |\n|------------|-------------|---------|---------------|\n| Primary    | Brand Blue  | #378DFF | 55, 141, 255  |\n| Secondary  | Light Blue  | #A5CAFF | 165, 202, 255 |\n\n\nTypography Table:\n\n| Element | Font Family | Weight  | Size (px) | Line Height |\n|---------|-------------|---------|-----------|-------------|\n| H1      | Inter       | Bold    | 48        | 1.2         |\n| H2      | Inter       | Bold    | 36        | 1.3         |\n| Body    | Inter       | Regular | 16        | 1.5         |\n\n\nButton States Table:\n\n| State     | Appearance              | Usage                          |\n|-----------|-------------------------|--------------------------------|\n| Primary   | Solid fill, primary     | Main call to action on a page  |\n| Secondary | Outline, primary color  | Secondary actions              |\n| Tertiary  | Text only              | Less important actions         |\n\nPDF Generation Best Practices\n\nProfessional Formatting:\n\nUse consistent heading hierarchy\nApply proper spacing between sections\nUtilize tables for structured data\nInclude visual examples where possible\n\nTypography:\n\nUse professional fonts (Inter, Roboto, or system fonts)\nMaintain consistent sizing hierarchy\nEnsure sufficient line height for readability\n\nColor Usage:\n\nShow color swatches with hex codes\nEnsure sufficient contrast for accessibility\nDocument color roles clearly\n\nOrganization:\n\nNumber sections clearly (1.0, 1.1, 2.0, etc.)\nInclude table of contents for longer guides\nUse page breaks appropriately\nAdd page numbers\n\nAccessibility:\n\nEnsure document is screen-reader friendly\nUse proper heading structure\nInclude alt text for images\nMaintain minimum font size of 12pt\nHandling Incomplete Information\n\nWhen information is missing or unclear:\n\nMake Reasonable Inferences:\n\nExtract colors from provided screenshots\nInfer typography from website analysis\nEstimate spacing based on visual patterns\n\nUse Placeholders:\n\n\"[Insert company mission statement]\" for unknown content\n\"[Link to design files]\" for unavailable resources\n\"Version 1.0\" and current date as defaults\n\nAsk Clarifying Questions:\n\n\"What is your company's mission statement?\"\n\"Do you have existing brand colors or should I extract them from the website?\"\n\"Are there specific accessibility requirements beyond WCAG 2.1 AA?\"\n\nProvide Templates:\n\nInclude example text for sections that need user input\nShow format for content they should provide\nGive guidance on what information would be ideal\nExample User Interactions\n\nExample 1: URL-Based Request User: \"Create a style guide for my website at example.com\" Process:\n\nFetch website with web_fetch\nAnalyze HTML/CSS for design system\nExtract colors, fonts, spacing\nStructure into standard template\nGenerate professional PDF\nProvide download link\n\nExample 2: Screenshot-Based Request User: \"Here are screenshots of my app. Create a style guide.\" [uploads images] Process:\n\nAnalyze images for visual elements\nExtract color palette\nIdentify typography patterns\nDocument component styles\nFill in template structure\nGenerate PDF with findings\nProvide download link\n\nExample 3: Comprehensive Request User: \"Create a style guide using my website URL, these brand colors [list], and our mission statement [text]\" Process:\n\nCombine all provided information\nFetch and analyze website\nIntegrate provided brand elements\nStructure complete style guide\nGenerate professional PDF\nProvide download link\nQuality Checklist\n\nBefore delivering the style guide PDF, verify:\n\n All sections are complete or marked as placeholders\n Color palette includes HEX and RGB values\n Typography specifications are detailed (family, weight, size, line height)\n Tables are properly formatted and aligned\n Accessibility requirements are documented\n Version number and date are included\n Resources section links are provided (even if placeholder)\n Changelog is started with version 1.0\n PDF is professionally formatted\n Document is ready for team distribution\nResources\n\nThis skill uses the following bundled resources:\n\nassets/template.pdf\n\nThe base template PDF that demonstrates the professional structure and formatting that all generated style guides should follow. This file serves as a reference for structure, section organization, and formatting standards.\n\nscripts/analyze_website.py\n\nPython script to extract design system information from websites, including colors, typography, and component patterns. Can be used to automatically gather design specifications from live URLs.\n\nreferences/design_system_examples.md\n\nReference document containing examples of well-structured design systems and style guides from leading companies. Use this for inspiration on content organization and presentation standards."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/TomsTools11/style-guide-generator",
    "publisherUrl": "https://clawhub.ai/TomsTools11/style-guide-generator",
    "owner": "TomsTools11",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/style-guide-generator",
    "downloadUrl": "https://openagent3.xyz/downloads/style-guide-generator",
    "agentUrl": "https://openagent3.xyz/skills/style-guide-generator/agent",
    "manifestUrl": "https://openagent3.xyz/skills/style-guide-generator/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/style-guide-generator/agent.md"
  }
}