[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSPZJRBASCXQXV71AVECV2":3,"skill-same:01M6CSPZJRBASCXQXV71AVECV2":69},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":21,"linkOnly":22,"markdownContent":23,"markdownBody":24,"frontMatter":25,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M6CSPZJRBASCXQXV71AVECV2","bad-yaml",null,"bitflight-devops\u002Fskilllint","bitflight-devops","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F83852040?v=4","01M6CSPE9HM6TQTDJPPR9ZGV3T","BitFlight DevOps - Jamie Nelson","01M6CSPEDJ8KR2QNV9RZX8R8RE",7,"MIT","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM002\u002Funclosed-brace\u002Fskills\u002Fbad-yaml\u002FSKILL.md",[],[18,19,20],"yaml","bad yaml","bad","2026-11-10 10:12:30",false,"---\r\nname: update-oo-component-documentation\r\ndescription: 'Update existing object-oriented component documentation following industry best practices and architectural documentation standards.'\r\n---\r\n\r\n# Update Standard OO Component Documentation\r\n\r\nUpdate the existing documentation file at: `${file}` by analyzing the corresponding component code.\r\n\r\nExtract the component path from the existing documentation's front matter (`component_path` field) or infer it from the documentation content. Analyze the current component implementation and update the documentation accordingly.\r\n\r\n**Documentation Standards:**\r\n\r\n- DOC-001: Follow C4 Model documentation levels (Context, Containers, Components, Code)\r\n- DOC-002: Align with Arc42 software architecture documentation template\r\n- DOC-003: Comply with IEEE 1016 Software Design Description standard\r\n- DOC-004: Use Agile Documentation principles (just enough documentation that adds value)\r\n- DOC-005: Target developers and maintainers as primary audience\r\n\r\n**Analysis Instructions:**\r\n\r\n- ANA-001: Read existing documentation to understand component context and structure\r\n- ANA-002: Identify component path from front matter or content analysis\r\n- ANA-003: Examine current source code files for class structures and inheritance\r\n- ANA-004: Compare existing documentation with current implementation\r\n- ANA-005: Identify design patterns and architectural changes\r\n- ANA-006: Update public APIs, interfaces, and dependencies\r\n- ANA-007: Recognize new\u002Fchanged creational\u002Fstructural\u002Fbehavioral patterns\r\n- ANA-008: Update method parameters, return values, exceptions\r\n- ANA-009: Reassess performance, security, reliability, maintainability\r\n- ANA-010: Update integration patterns and data flow\r\n\r\n**Language-Specific Optimizations:**\r\n\r\n- LNG-001: **C#\u002F.NET** - async\u002Fawait, dependency injection, configuration, disposal\r\n- LNG-002: **Java** - Spring framework, annotations, exception handling, packaging\r\n- LNG-003: **TypeScript\u002FJavaScript** - modules, async patterns, types, npm\r\n- LNG-004: **Python** - packages, virtual environments, type hints, testing\r\n\r\n**Update Strategy:**\r\n\r\n- UPD-001: Preserve existing documentation structure and format\r\n- UPD-002: Update `last_updated` field to current date\r\n- UPD-003: Maintain version history in front matter if present\r\n- UPD-004: Add new sections if component has significantly expanded\r\n- UPD-005: Mark deprecated features or breaking changes\r\n- UPD-006: Update examples to reflect current API\r\n- UPD-007: Refresh dependency lists and versions\r\n- UPD-008: Update mermaid diagrams to reflect current architecture\r\n\r\n**Error Handling:**\r\n\r\n- ERR-001: Documentation file doesn't exist - provide guidance on file location\r\n- ERR-002: Component path not found in documentation - request clarification\r\n- ERR-003: Source code has moved - suggest updated paths\r\n- ERR-004: Major architectural changes - highlight breaking changes\r\n- ERR-005: Insufficient access to source - document limitations\r\n\r\n**Output Format:**\r\n\r\nUpdate the existing Markdown file maintaining its structure while refreshing content to match current implementation. Preserve formatting, heading hierarchy, and existing organizational decisions.\r\n\r\n**Required Documentation Structure:**\r\n\r\nUpdate the existing documentation following the same template structure, ensuring all sections reflect current implementation:\r\n\r\n```md\r\n---\r\ntitle: [Component Name] - Technical Documentation\r\ncomponent_path: [Current component path]\r\nversion: [Updated version if applicable]\r\ndate_created: [Original creation date - preserve]\r\nlast_updated: [YYYY-MM-DD - update to current date]\r\nowner: [Preserve existing or update if changed]\r\ntags: [Update tags as needed based on current functionality]\r\n---\r\n\r\n# [Component Name] Documentation\r\n\r\n[Update introduction to reflect current component purpose and capabilities]\r\n\r\n## 1. Component Overview\r\n\r\n### Purpose\u002FResponsibility\r\n- OVR-001: Update component's primary responsibility\r\n- OVR-002: Refresh scope (included\u002Fexcluded functionality)\r\n- OVR-003: Update system context and relationships\r\n\r\n## 2. Architecture Section\r\n\r\n- ARC-001: Update design patterns used (Repository, Factory, Observer, etc.)\r\n- ARC-002: Refresh internal and external dependencies with current purposes\r\n- ARC-003: Update component interactions and relationships\r\n- ARC-004: Update visual diagrams (UML class, sequence, component)\r\n- ARC-005: Refresh mermaid diagram showing current component structure, relationships, and dependencies\r\n\r\n### Component Structure and Dependencies Diagram\r\n\r\nUpdate the mermaid diagram to show current:\r\n- **Component structure** - Current classes, interfaces, and their relationships\r\n- **Internal dependencies** - How components currently interact within the system\r\n- **External dependencies** - Current external libraries, services, databases, APIs\r\n- **Data flow** - Current direction of dependencies and interactions\r\n- **Inheritance\u002Fcomposition** - Current class hierarchies and composition relationships\r\n\r\n```mermaid\r\n[Update diagram to reflect current architecture]\r\n```\r\n\r\n## 3. Interface Documentation\r\n\r\n- INT-001: Update all public interfaces and current usage patterns\r\n- INT-002: Refresh method\u002Fproperty reference table with current API\r\n- INT-003: Update events\u002Fcallbacks\u002Fnotification mechanisms\r\n\r\n| Method\u002FProperty | Purpose | Parameters | Return Type | Usage Notes |\r\n|-----------------|---------|------------|-------------|-------------|\r\n| [Update table with current API] | | | | |\r\n\r\n## 4. Implementation Details\r\n\r\n- IMP-001: Update main implementation classes and current responsibilities\r\n- IMP-002: Refresh configuration requirements and initialization patterns\r\n- IMP-003: Update key algorithms and business logic\r\n- IMP-004: Update performance characteristics and bottlenecks\r\n\r\n## 5. Usage Examples\r\n\r\n### Basic Usage\r\n\r\n```csharp\r\n\u002F\u002F Update basic usage example to current API\r\n```\r\n\r\n### Advanced Usage\r\n\r\n```csharp\r\n\u002F\u002F Update advanced configuration patterns to current implementation\r\n```\r\n\r\n- USE-001: Update basic usage examples\r\n- USE-002: Refresh advanced configuration patterns\r\n- USE-003: Update best practices and recommended patterns\r\n\r\n## 6. Quality Attributes\r\n\r\n- QUA-001: Update security (authentication, authorization, data protection)\r\n- QUA-002: Refresh performance (characteristics, scalability, resource usage)\r\n- QUA-003: Update reliability (error handling, fault tolerance, recovery)\r\n- QUA-004: Refresh maintainability (standards, testing, documentation)\r\n- QUA-005: Update extensibility (extension points, customization options)\r\n\r\n## 7. Reference Information\r\n\r\n- REF-001: Update dependencies with current versions and purposes\r\n- REF-002: Refresh configuration options reference\r\n- REF-003: Update testing guidelines and mock setup\r\n- REF-004: Refresh troubleshooting (common issues, error messages)\r\n- REF-005: Update related documentation links\r\n- REF-006: Add change history and migration notes for this update\r\n\r\n```\r\n","# Update Standard OO Component Documentation\r\n\r\nUpdate the existing documentation file at: `${file}` by analyzing the corresponding component code.\r\n\r\nExtract the component path from the existing documentation's front matter (`component_path` field) or infer it from the documentation content. Analyze the current component implementation and update the documentation accordingly.\r\n\r\n**Documentation Standards:**\r\n\r\n- DOC-001: Follow C4 Model documentation levels (Context, Containers, Components, Code)\r\n- DOC-002: Align with Arc42 software architecture documentation template\r\n- DOC-003: Comply with IEEE 1016 Software Design Description standard\r\n- DOC-004: Use Agile Documentation principles (just enough documentation that adds value)\r\n- DOC-005: Target developers and maintainers as primary audience\r\n\r\n**Analysis Instructions:**\r\n\r\n- ANA-001: Read existing documentation to understand component context and structure\r\n- ANA-002: Identify component path from front matter or content analysis\r\n- ANA-003: Examine current source code files for class structures and inheritance\r\n- ANA-004: Compare existing documentation with current implementation\r\n- ANA-005: Identify design patterns and architectural changes\r\n- ANA-006: Update public APIs, interfaces, and dependencies\r\n- ANA-007: Recognize new\u002Fchanged creational\u002Fstructural\u002Fbehavioral patterns\r\n- ANA-008: Update method parameters, return values, exceptions\r\n- ANA-009: Reassess performance, security, reliability, maintainability\r\n- ANA-010: Update integration patterns and data flow\r\n\r\n**Language-Specific Optimizations:**\r\n\r\n- LNG-001: **C#\u002F.NET** - async\u002Fawait, dependency injection, configuration, disposal\r\n- LNG-002: **Java** - Spring framework, annotations, exception handling, packaging\r\n- LNG-003: **TypeScript\u002FJavaScript** - modules, async patterns, types, npm\r\n- LNG-004: **Python** - packages, virtual environments, type hints, testing\r\n\r\n**Update Strategy:**\r\n\r\n- UPD-001: Preserve existing documentation structure and format\r\n- UPD-002: Update `last_updated` field to current date\r\n- UPD-003: Maintain version history in front matter if present\r\n- UPD-004: Add new sections if component has significantly expanded\r\n- UPD-005: Mark deprecated features or breaking changes\r\n- UPD-006: Update examples to reflect current API\r\n- UPD-007: Refresh dependency lists and versions\r\n- UPD-008: Update mermaid diagrams to reflect current architecture\r\n\r\n**Error Handling:**\r\n\r\n- ERR-001: Documentation file doesn't exist - provide guidance on file location\r\n- ERR-002: Component path not found in documentation - request clarification\r\n- ERR-003: Source code has moved - suggest updated paths\r\n- ERR-004: Major architectural changes - highlight breaking changes\r\n- ERR-005: Insufficient access to source - document limitations\r\n\r\n**Output Format:**\r\n\r\nUpdate the existing Markdown file maintaining its structure while refreshing content to match current implementation. Preserve formatting, heading hierarchy, and existing organizational decisions.\r\n\r\n**Required Documentation Structure:**\r\n\r\nUpdate the existing documentation following the same template structure, ensuring all sections reflect current implementation:\r\n\r\n```md\r\n---\r\ntitle: [Component Name] - Technical Documentation\r\ncomponent_path: [Current component path]\r\nversion: [Updated version if applicable]\r\ndate_created: [Original creation date - preserve]\r\nlast_updated: [YYYY-MM-DD - update to current date]\r\nowner: [Preserve existing or update if changed]\r\ntags: [Update tags as needed based on current functionality]\r\n---\r\n\r\n# [Component Name] Documentation\r\n\r\n[Update introduction to reflect current component purpose and capabilities]\r\n\r\n## 1. Component Overview\r\n\r\n### Purpose\u002FResponsibility\r\n- OVR-001: Update component's primary responsibility\r\n- OVR-002: Refresh scope (included\u002Fexcluded functionality)\r\n- OVR-003: Update system context and relationships\r\n\r\n## 2. Architecture Section\r\n\r\n- ARC-001: Update design patterns used (Repository, Factory, Observer, etc.)\r\n- ARC-002: Refresh internal and external dependencies with current purposes\r\n- ARC-003: Update component interactions and relationships\r\n- ARC-004: Update visual diagrams (UML class, sequence, component)\r\n- ARC-005: Refresh mermaid diagram showing current component structure, relationships, and dependencies\r\n\r\n### Component Structure and Dependencies Diagram\r\n\r\nUpdate the mermaid diagram to show current:\r\n- **Component structure** - Current classes, interfaces, and their relationships\r\n- **Internal dependencies** - How components currently interact within the system\r\n- **External dependencies** - Current external libraries, services, databases, APIs\r\n- **Data flow** - Current direction of dependencies and interactions\r\n- **Inheritance\u002Fcomposition** - Current class hierarchies and composition relationships\r\n\r\n```mermaid\r\n[Update diagram to reflect current architecture]\r\n```\r\n\r\n## 3. Interface Documentation\r\n\r\n- INT-001: Update all public interfaces and current usage patterns\r\n- INT-002: Refresh method\u002Fproperty reference table with current API\r\n- INT-003: Update events\u002Fcallbacks\u002Fnotification mechanisms\r\n\r\n| Method\u002FProperty | Purpose | Parameters | Return Type | Usage Notes |\r\n|-----------------|---------|------------|-------------|-------------|\r\n| [Update table with current API] | | | | |\r\n\r\n## 4. Implementation Details\r\n\r\n- IMP-001: Update main implementation classes and current responsibilities\r\n- IMP-002: Refresh configuration requirements and initialization patterns\r\n- IMP-003: Update key algorithms and business logic\r\n- IMP-004: Update performance characteristics and bottlenecks\r\n\r\n## 5. Usage Examples\r\n\r\n### Basic Usage\r\n\r\n```csharp\r\n\u002F\u002F Update basic usage example to current API\r\n```\r\n\r\n### Advanced Usage\r\n\r\n```csharp\r\n\u002F\u002F Update advanced configuration patterns to current implementation\r\n```\r\n\r\n- USE-001: Update basic usage examples\r\n- USE-002: Refresh advanced configuration patterns\r\n- USE-003: Update best practices and recommended patterns\r\n\r\n## 6. Quality Attributes\r\n\r\n- QUA-001: Update security (authentication, authorization, data protection)\r\n- QUA-002: Refresh performance (characteristics, scalability, resource usage)\r\n- QUA-003: Update reliability (error handling, fault tolerance, recovery)\r\n- QUA-004: Refresh maintainability (standards, testing, documentation)\r\n- QUA-005: Update extensibility (extension points, customization options)\r\n\r\n## 7. Reference Information\r\n\r\n- REF-001: Update dependencies with current versions and purposes\r\n- REF-002: Refresh configuration options reference\r\n- REF-003: Update testing guidelines and mock setup\r\n- REF-004: Refresh troubleshooting (common issues, error messages)\r\n- REF-005: Update related documentation links\r\n- REF-006: Add change history and migration notes for this update\r\n\r\n```\r\n",{"name":26,"description":27},"update-oo-component-documentation","Update existing object-oriented component documentation following industry best practices and architectural documentation standards.","main","16528f2130fc4b890558a1fccd590ad29e9bae7a","packages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM002\u002Funclosed-brace\u002Fskills\u002Fbad-yaml",0,"https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint","https:\u002F\u002Fgithub.com\u002Fbitflight-devops","Public repositories of DevOps tools, scripts, integrations, and templates","2026-11-09 14:16:32",{"source":7,"skillName":26,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add bitflight-devops\u002Fskilllint --skill update-oo-component-documentation",{"tool":42,"command":43},"bunx","bunx skills add bitflight-devops\u002Fskilllint --skill update-oo-component-documentation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add bitflight-devops\u002Fskilllint --skill update-oo-component-documentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM002\u002Funclosed-brace\u002Fskills\u002Fbad-yaml\u002FSKILL.md",true,[50,55,61,64],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":31,"sourceHtmlUrl":54},"assets\u002F.gitkeep","ASSET","资产文件","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM002\u002Funclosed-brace\u002Fskills\u002Fbad-yaml\u002Fassets\u002F.gitkeep",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"eval_queries.json","REFERENCE","参考文档",15,"https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM002\u002Funclosed-brace\u002Fskills\u002Fbad-yaml\u002Feval_queries.json",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":31,"sourceHtmlUrl":63},"references\u002F.gitkeep","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM002\u002Funclosed-brace\u002Fskills\u002Fbad-yaml\u002Freferences\u002F.gitkeep",{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":31,"sourceHtmlUrl":68},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Ffailing-examples\u002FFM002\u002Funclosed-brace\u002Fskills\u002Fbad-yaml\u002Fscripts\u002F.gitkeep",[70,83,109,128,138,151],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":21},"01M6CSQYQKKT3AP6J6NTT1RYJG","fixable-skill","Exercise grouped Action fix findings.","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Faction\u002Fskills\u002Ffixable-skill\u002FSKILL.md",[],[77,78,79,80,81,82],"fixable skill","action","exercise","fix findings","fix","read",{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":21},"01M6CSQWBMT9000HH2A7KR1TCC","skilllint","Use the skilllint CLI to validate, explain, and fix agent plugins, skills, agents, commands, and platform files. Use when asked to lint agent artifacts, investigate a skilllint rule ID, or verify a plugin before commit.","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fplugins\u002Fagentskills-skilllint\u002Fskills\u002Fskilllint\u002FSKILL.md",[],[85,90,91,92,93,94,95,96,97,98,99,81,100,101,102,103,104,105,106,107,108],"explain","cli","commit","validate","plugin","lint","artifacts","plugins","verify","investigate","use","files","commands","platform","id","rule","path","agent plugins","when",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":120,"publishedAt":21},"01M6CSQTRYRZN792TK6FV6PDAA","my-skill","Use this skill when you need to verify valid name pattern compliance.","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Fpassing-examples\u002FFM010\u002Fvalid-name-pattern\u002Fskills\u002Fmy-skill\u002FSKILL.md",[115],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[121,122,123,108,124,125,126,98,100,127],"my","my skill","you","name","valid","compliance","pattern",{"skillNo":129,"name":111,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":134,"publishedAt":21},"01M6CSQSAR0FC01CBKBXSTYQCD","Use this skill when you need to verify quoted descriptions with colons: example.","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Fpassing-examples\u002FFM009\u002Fquoted-description\u002Fskills\u002Fmy-skill\u002FSKILL.md",[133],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[121,122,98,100,135,136,123,137,108],"example","with","quoted",{"skillNo":139,"name":111,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":21},"01M6CSQQK9TV19JTYPV242XR1P","Use this skill when you need to verify CSV string format for tools.","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Fpassing-examples\u002FFM007\u002Ftools-as-csv-string\u002Fskills\u002Fmy-skill\u002FSKILL.md",[143],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[121,122,123,145,146,98,147,148,82,100,149,150,108],"csv","Tools","format","grep","STRING","for",{"skillNo":152,"name":111,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":21},"01M6CSQP4X044W2FZXDMVGWHPM","Use this skill when you need to verify valid enum field values.","https:\u002F\u002Fgithub.com\u002Fbitflight-devops\u002Fskilllint\u002Fblob\u002Fmain\u002Fpackages\u002Fskilllint\u002Ftests\u002Ffixtures\u002Fproviders\u002Fagentskills\u002Fpassing-examples\u002FFM006\u002Fvalid-context-value\u002Fskills\u002Fmy-skill\u002FSKILL.md",[156],{"categoryNo":116,"categoryName":117,"taxonomyType":118,"taxonomyTypeDesc":119},[122,121,125,98,100,123,158,159,108],"values","fork"]