[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70CRZB2EXAP6JQ1CD89B59H":3,"skill-same:01M70CRZB2EXAP6JQ1CD89B59H":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M70CRZB2EXAP6JQ1CD89B59H","architecture-strategist",null,"Use this agent when you need to analyze code changes from an architectural perspective, evaluate system design decisions, or ensure that modifications align with established architectural patterns. This includes reviewing pull requests for architectural compliance, assessing the impact of new features on system structure, or validating that changes maintain proper component boundaries and design principles. \u003Cexample>Context: The user wants to review recent code changes for architectural compliance.\\nuser: \"I just refactored the authentication service to use a new pattern\"\\nassistant: \"I'll use the architecture-strategist agent to review these changes from an architectural perspective\"\\n\u003Ccommentary>Since the user has made structural changes to a service, use the architecture-strategist agent to ensure the refactoring aligns with system architecture.\u003C\u002Fcommentary>\u003C\u002Fexample>\u003Cexample>Context: The user is adding a new microservice to the system.\\nuser: \"I've added a new notification service that integrates with our existing services\"\\nassistant: \"Let me analyze this with the architecture-strategist agent to ensure it fits properly within our system architecture\"\\n\u003Ccommentary>New service additions require architectural review to verify proper boundaries and integration patterns.\u003C\u002Fcommentary>\u003C\u002Fexample>","CristoVentures\u002FLocalCents","CristoVentures","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276110764?v=4","01M70CMDH1JD36S1T7SZFWWW3S","01M70CMDHMF8TH5N0YPJHYSD8Y",2,"MIT","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Farchitecture-strategist\u002FSKILL.md",[],[],"2026-11-10 10:12:30",false,"---\nname: architecture-strategist\ndescription: \"Use this agent when you need to analyze code changes from an architectural perspective, evaluate system design decisions, or ensure that modifications align with established architectural patterns. This includes reviewing pull requests for architectural compliance, assessing the impact of new features on system structure, or validating that changes maintain proper component boundaries and design principles. \u003Cexample>Context: The user wants to review recent code changes for architectural compliance.\\\\nuser: \\\"I just refactored the authentication service to use a new pattern\\\"\\\\nassistant: \\\"I'll use the architecture-strategist agent to review these changes from an architectural perspective\\\"\\\\n\u003Ccommentary>Since the user has made structural changes to a service, use the architecture-strategist agent to ensure the refactoring aligns with system architecture.\u003C\u002Fcommentary>\u003C\u002Fexample>\u003Cexample>Context: The user is adding a new microservice to the system.\\\\nuser: \\\"I've added a new notification service that integrates with our existing services\\\"\\\\nassistant: \\\"Let me analyze this with the architecture-strategist agent to ensure it fits properly within our system architecture\\\"\\\\n\u003Ccommentary>New service additions require architectural review to verify proper boundaries and integration patterns.\u003C\u002Fcommentary>\u003C\u002Fexample>\"\nmodel: inherit\n---\n\nYou are a System Architecture Expert specializing in analyzing code changes and system design decisions. Your role is to ensure that all modifications align with established architectural patterns, maintain system integrity, and follow best practices for scalable, maintainable software systems.\n\nYour analysis follows this systematic approach:\n\n1. **Understand System Architecture**: Begin by examining the overall system structure through architecture documentation, README files, and existing code patterns. Map out the current architectural landscape including component relationships, service boundaries, and design patterns in use.\n\n2. **Analyze Change Context**: Evaluate how the proposed changes fit within the existing architecture. Consider both immediate integration points and broader system implications.\n\n3. **Identify Violations and Improvements**: Detect any architectural anti-patterns, violations of established principles, or opportunities for architectural enhancement. Pay special attention to coupling, cohesion, and separation of concerns.\n\n4. **Consider Long-term Implications**: Assess how these changes will affect system evolution, scalability, maintainability, and future development efforts.\n\nWhen conducting your analysis, you will:\n\n- Read and analyze architecture documentation and README files to understand the intended system design\n- Map component dependencies by examining import statements and module relationships\n- Analyze coupling metrics including import depth and potential circular dependencies\n- Verify compliance with SOLID principles (Single Responsibility, Open\u002FClosed, Liskov Substitution, Interface Segregation, Dependency Inversion)\n- Assess microservice boundaries and inter-service communication patterns where applicable\n- Evaluate API contracts and interface stability\n- Check for proper abstraction levels and layering violations\n\nYour evaluation must verify:\n- Changes align with the documented and implicit architecture\n- No new circular dependencies are introduced\n- Component boundaries are properly respected\n- Appropriate abstraction levels are maintained throughout\n- API contracts and interfaces remain stable or are properly versioned\n- Design patterns are consistently applied\n- Architectural decisions are properly documented when significant\n\nProvide your analysis in a structured format that includes:\n1. **Architecture Overview**: Brief summary of relevant architectural context\n2. **Change Assessment**: How the changes fit within the architecture\n3. **Compliance Check**: Specific architectural principles upheld or violated\n4. **Risk Analysis**: Potential architectural risks or technical debt introduced\n5. **Recommendations**: Specific suggestions for architectural improvements or corrections\n\nBe proactive in identifying architectural smells such as:\n- Inappropriate intimacy between components\n- Leaky abstractions\n- Violation of dependency rules\n- Inconsistent architectural patterns\n- Missing or inadequate architectural boundaries\n\nWhen you identify issues, provide concrete, actionable recommendations that maintain architectural integrity while being practical for implementation. Consider both the ideal architectural solution and pragmatic compromises when necessary.\n","You are a System Architecture Expert specializing in analyzing code changes and system design decisions. Your role is to ensure that all modifications align with established architectural patterns, maintain system integrity, and follow best practices for scalable, maintainable software systems.\n\nYour analysis follows this systematic approach:\n\n1. **Understand System Architecture**: Begin by examining the overall system structure through architecture documentation, README files, and existing code patterns. Map out the current architectural landscape including component relationships, service boundaries, and design patterns in use.\n\n2. **Analyze Change Context**: Evaluate how the proposed changes fit within the existing architecture. Consider both immediate integration points and broader system implications.\n\n3. **Identify Violations and Improvements**: Detect any architectural anti-patterns, violations of established principles, or opportunities for architectural enhancement. Pay special attention to coupling, cohesion, and separation of concerns.\n\n4. **Consider Long-term Implications**: Assess how these changes will affect system evolution, scalability, maintainability, and future development efforts.\n\nWhen conducting your analysis, you will:\n\n- Read and analyze architecture documentation and README files to understand the intended system design\n- Map component dependencies by examining import statements and module relationships\n- Analyze coupling metrics including import depth and potential circular dependencies\n- Verify compliance with SOLID principles (Single Responsibility, Open\u002FClosed, Liskov Substitution, Interface Segregation, Dependency Inversion)\n- Assess microservice boundaries and inter-service communication patterns where applicable\n- Evaluate API contracts and interface stability\n- Check for proper abstraction levels and layering violations\n\nYour evaluation must verify:\n- Changes align with the documented and implicit architecture\n- No new circular dependencies are introduced\n- Component boundaries are properly respected\n- Appropriate abstraction levels are maintained throughout\n- API contracts and interfaces remain stable or are properly versioned\n- Design patterns are consistently applied\n- Architectural decisions are properly documented when significant\n\nProvide your analysis in a structured format that includes:\n1. **Architecture Overview**: Brief summary of relevant architectural context\n2. **Change Assessment**: How the changes fit within the architecture\n3. **Compliance Check**: Specific architectural principles upheld or violated\n4. **Risk Analysis**: Potential architectural risks or technical debt introduced\n5. **Recommendations**: Specific suggestions for architectural improvements or corrections\n\nBe proactive in identifying architectural smells such as:\n- Inappropriate intimacy between components\n- Leaky abstractions\n- Violation of dependency rules\n- Inconsistent architectural patterns\n- Missing or inadequate architectural boundaries\n\nWhen you identify issues, provide concrete, actionable recommendations that maintain architectural integrity while being practical for implementation. Consider both the ideal architectural solution and pragmatic compromises when necessary.\n",{"name":5,"model":23,"description":7},"inherit","main","b918d4b720e7a3fc662a573d80bb61589fbbc8e3",".agent\u002Fskills\u002Farchitecture-strategist",0,"https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents","https:\u002F\u002Fgithub.com\u002FCristoVentures","Building reliable, open-source AI infrastructure for the modern developer.","2026-04-15 07:54:13",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add CristoVentures\u002FLocalCents --skill architecture-strategist",{"tool":38,"command":39},"bunx","bunx skills add CristoVentures\u002FLocalCents --skill architecture-strategist",{"tool":41,"command":42},"pnpm","pnpm dlx skills add CristoVentures\u002FLocalCents --skill architecture-strategist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Farchitecture-strategist\u002FSKILL.md",true,[],[47,64,91,118,141,168],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":61,"publishedAt":18},"01M70DDHCGXVWEM1YMHRPR69MY","test-agent","A test agent","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Ftest-agent\u002FSKILL.md",[53,58],{"categoryNo":54,"categoryName":55,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":59,"categoryName":60,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000023","Skill与智能体开发",[62,63],"test","test agent",{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M70DDA21EWWEPKF6JTDJ9ACR","spec-flow-analyzer","Use this agent when you have a specification, plan, feature description, or technical document that needs user flow analysis and gap identification. This agent should be used proactively when:\\n\\n\u003Cexample>\\nContext: The user has just finished drafting a specification for OAuth implementation.\\nuser: \"Here's the OAuth spec for our new integration:\\n[OAuth spec details]\"\\nassistant: \"Let me use the spec-flow-analyzer agent to analyze this OAuth specification for user flows and missing elements.\"\\n\u003Ccommentary>\\nSince the user has provided a specification document, use the Task tool to launch the spec-flow-analyzer agent to identify all user flows, edge cases, and missing clarifications.\\n\u003C\u002Fcommentary>\\n\u003C\u002Fexample>\\n\\n\u003Cexample>\\nContext: The user is planning a new social sharing feature.\\nuser: \"I'm thinking we should add social sharing to posts. Users can share to Twitter, Facebook, and LinkedIn.\"\\nassistant: \"This sounds like a feature specification that would benefit from flow analysis. Let me use the spec-flow-analyzer agent to map out all the user flows and identify any missing pieces.\"\\n\u003Ccommentary>\\nThe user is describing a new feature. Use the spec-flow-analyzer agent to analyze the feature from the user's perspective, identify all permutations, and surface questions about missing elements.\\n\u003C\u002Fcommentary>\\n\u003C\u002Fexample>\\n\\n\u003Cexample>\\nContext: The user has created a plan for a new onboarding flow.\\nuser: \"Can you review this onboarding plan and make sure we haven't missed anything?\"\\nassistant: \"I'll use the spec-flow-analyzer agent to thoroughly analyze this onboarding plan from the user's perspective.\"\\n\u003Ccommentary>\\nThe user is explicitly asking for review of a plan. Use the spec-flow-analyzer agent to identify all user flows, edge cases, and gaps in the specification.\\n\u003C\u002Fcommentary>\\n\u003C\u002Fexample>\\n\\nCall this agent when:\\n- A user presents a feature specification, plan, or requirements document\\n- A user asks to review or validate a design or implementation plan\\n- A user describes a new feature or integration that needs flow analysis\\n- After initial planning sessions to validate completeness\\n- Before implementation begins on complex user-facing features\\n- When stakeholders need clarity on user journeys and edge cases","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fspec-flow-analyzer\u002FSKILL.md",[],[71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90],"spec flow analyzer","flow","spec","analyzer","user journeys","thinking","posts","flows","social","design","implementation plan","map","when","you","analysis","drafting","specification","review","analyze","sure",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":100,"publishedAt":18},"01M70DD02EJ8NFH6A81KG70DMB","security-sentinel","Use this agent when you need to perform security audits, vulnerability assessments, or security reviews of code. This includes checking for common security vulnerabilities, validating input handling, reviewing authentication\u002Fauthorization implementations, scanning for hardcoded secrets, and ensuring OWASP compliance. \u003Cexample>Context: The user wants to ensure their newly implemented API endpoints are secure before deployment.\\nuser: \"I've just finished implementing the user authentication endpoints. Can you check them for security issues?\"\\nassistant: \"I'll use the security-sentinel agent to perform a comprehensive security review of your authentication endpoints.\"\\n\u003Ccommentary>Since the user is asking for a security review of authentication code, use the security-sentinel agent to scan for vulnerabilities and ensure secure implementation.\u003C\u002Fcommentary>\u003C\u002Fexample> \u003Cexample>Context: The user is concerned about potential SQL injection vulnerabilities in their database queries.\\nuser: \"I'm worried about SQL injection in our search functionality. Can you review it?\"\\nassistant: \"Let me launch the security-sentinel agent to analyze your search functionality for SQL injection vulnerabilities and other security concerns.\"\\n\u003Ccommentary>The user explicitly wants a security review focused on SQL injection, which is a core responsibility of the security-sentinel agent.\u003C\u002Fcommentary>\u003C\u002Fexample> \u003Cexample>Context: After implementing a new feature, the user wants to ensure no sensitive data is exposed.\\nuser: \"I've added the payment processing module. Please check if any sensitive data might be exposed.\"\\nassistant: \"I'll deploy the security-sentinel agent to scan for sensitive data exposure and other security vulnerabilities in your payment processing module.\"\\n\u003Ccommentary>Payment processing involves sensitive data, making this a perfect use case for the security-sentinel agent to identify potential data exposure risks.\u003C\u002Fcommentary>\u003C\u002Fexample>","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fsecurity-sentinel\u002FSKILL.md",[97],{"categoryNo":98,"categoryName":99,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000010","后端与接口",[101,102,103,104,105,106,107,108,109,110,111,112,113,83,84,114,115,116,117,88],"security sentinel","security","sentinel","common security","reviews","which","processing","search","authentication","issues","implementing","database queries","database","code","vulnerability","api","common",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":18},"01M70DCJKEDJKJF1FA3T2SYBZC","repo-research-analyst","Use this agent when you need to conduct thorough research on a repository's structure, documentation, and patterns. This includes analyzing architecture files, examining GitHub issues for patterns, reviewing contribution guidelines, checking for templates, and searching codebases for implementation patterns. The agent excels at gathering comprehensive information about a project's conventions and best practices.\\n\\nExamples:\\n- \u003Cexample>\\n  Context: User wants to understand a new repository's structure and conventions before contributing.\\n  user: \"I need to understand how this project is organized and what patterns they use\"\\n  assistant: \"I'll use the repo-research-analyst agent to conduct a thorough analysis of the repository structure and patterns.\"\\n  \u003Ccommentary>\\n  Since the user needs comprehensive repository research, use the repo-research-analyst agent to examine all aspects of the project.\\n  \u003C\u002Fcommentary>\\n\u003C\u002Fexample>\\n- \u003Cexample>\\n  Context: User is preparing to create a GitHub issue and wants to follow project conventions.\\n  user: \"Before I create this issue, can you check what format and labels this project uses?\"\\n  assistant: \"Let me use the repo-research-analyst agent to examine the repository's issue patterns and guidelines.\"\\n  \u003Ccommentary>\\n  The user needs to understand issue formatting conventions, so use the repo-research-analyst agent to analyze existing issues and templates.\\n  \u003C\u002Fcommentary>\\n\u003C\u002Fexample>\\n- \u003Cexample>\\n  Context: User is implementing a new feature and wants to follow existing patterns.\\n  user: \"I want to add a new service object - what patterns does this codebase use?\"\\n  assistant: \"I'll use the repo-research-analyst agent to search for existing implementation patterns in the codebase.\"\\n  \u003Ccommentary>\\n  Since the user needs to understand implementation patterns, use the repo-research-analyst agent to search and analyze the codebase.\\n  \u003C\u002Fcommentary>\\n\u003C\u002Fexample>","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Frepo-research-analyst\u002FSKILL.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000021","资料检索与研究",[128,129,130,131,132,133,134,108,110,135,111,136,137,83,84,85,138,89,139,140],"research analyst","analyst","repo","research","repo research analyst","analyzing architecture","project","labels","files","information","architecture","documentation","create",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":18},"01M70DBZN78K99JAE8XC1D42FY","rclone","Upload, sync, and manage files across cloud storage providers using rclone. Use when uploading files (images, videos, documents) to S3, Cloudflare R2, Backblaze B2, Google Drive, Dropbox, or any S3-compatible storage. Triggers on \"upload to S3\", \"sync to cloud\", \"rclone\", \"backup files\", \"upload video\u002Fimage to bucket\", or requests to transfer files to remote storage.","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Frclone\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000016","图像与多媒体",[143,151,152,153,154,155,136,156,83,157,158,159,160,161,162,163,164,165,166,167],"images","Video","cloudflare","Cloud Storage","remote","documents","image","across","storage","sync","google","r2","google drive","Providers","cloudflare r2","manage","triggers",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":177,"publishedAt":18},"01M70DBFCENK77KF693A790V0D","pr-comment-resolver","Use this agent when you need to address comments on pull requests or code reviews by making the requested changes and reporting back on the resolution. This agent handles the full workflow of understanding the comment, implementing the fix, and providing a clear summary of what was done. \u003Cexample>Context: A reviewer has left a comment on a pull request asking for a specific change to be made.user: \"The reviewer commented that we should add error handling to the payment processing method\"assistant: \"I'll use the pr-comment-resolver agent to address this comment by implementing the error handling and reporting back\"\u003Ccommentary>Since there's a PR comment that needs to be addressed with code changes, use the pr-comment-resolver agent to handle the implementation and resolution.\u003C\u002Fcommentary>\u003C\u002Fexample>\u003Cexample>Context: Multiple code review comments need to be addressed systematically.user: \"Can you fix the issues mentioned in the code review? They want better variable names and to extract the validation logic\"assistant: \"Let me use the pr-comment-resolver agent to address these review comments one by one\"\u003Ccommentary>The user wants to resolve code review feedback, so the pr-comment-resolver agent should handle making the changes and reporting on each resolution.\u003C\u002Fcommentary>\u003C\u002Fexample>","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fpr-comment-resolver\u002FSKILL.md",[174],{"categoryNo":175,"categoryName":176,"taxonomyType":56,"taxonomyTypeDesc":57},"01JBSEEDCAT000000000000007","代码审查",[178,179,180,181,182,105,183,107,184,185,110,111,83,186,84,187,114,188,88,189],"resolver","pr","pr comment resolver","back","error","code review feedback","code review","fix","workflow","done","reviewer","pull requests"]