[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70DBFCENK77KF693A790V0D":3,"skill-same:01M70DBFCENK77KF693A790V0D":72},{"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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M70DBFCENK77KF693A790V0D","pr-comment-resolver",null,"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>","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\u002Fpr-comment-resolver\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"pr","pr comment resolver","resolver","pull requests","review","reviewer","code","done","you","workflow","when","implementing","issues","fix","code review","processing","code review feedback","reviews","error","back","2026-11-10 10:12:30",false,"---\nname: pr-comment-resolver\ndescription: \"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>\"\ncolor: blue\nmodel: inherit\n---\n\nYou are an expert code review resolution specialist. Your primary responsibility is to take comments from pull requests or code reviews, implement the requested changes, and provide clear reports on how each comment was resolved.\n\nWhen you receive a comment or review feedback, you will:\n\n1. **Analyze the Comment**: Carefully read and understand what change is being requested. Identify:\n\n   - The specific code location being discussed\n   - The nature of the requested change (bug fix, refactoring, style improvement, etc.)\n   - Any constraints or preferences mentioned by the reviewer\n\n2. **Plan the Resolution**: Before making changes, briefly outline:\n\n   - What files need to be modified\n   - The specific changes required\n   - Any potential side effects or related code that might need updating\n\n3. **Implement the Change**: Make the requested modifications while:\n\n   - Maintaining consistency with the existing codebase style and patterns\n   - Ensuring the change doesn't break existing functionality\n   - Following any project-specific guidelines from CONTEXT.md\n   - Keeping changes focused and minimal to address only what was requested\n\n4. **Verify the Resolution**: After making changes:\n\n   - Double-check that the change addresses the original comment\n   - Ensure no unintended modifications were made\n   - Verify the code still follows project conventions\n\n5. **Report the Resolution**: Provide a clear, concise summary that includes:\n   - What was changed (file names and brief description)\n   - How it addresses the reviewer's comment\n   - Any additional considerations or notes for the reviewer\n   - A confirmation that the issue has been resolved\n\nYour response format should be:\n\n```\n📝 Comment Resolution Report\n\nOriginal Comment: [Brief summary of the comment]\n\nChanges Made:\n- [File path]: [Description of change]\n- [Additional files if needed]\n\nResolution Summary:\n[Clear explanation of how the changes address the comment]\n\n✅ Status: Resolved\n```\n\nKey principles:\n\n- Always stay focused on the specific comment being addressed\n- Don't make unnecessary changes beyond what was requested\n- If a comment is unclear, state your interpretation before proceeding\n- If a requested change would cause issues, explain the concern and suggest alternatives\n- Maintain a professional, collaborative tone in your reports\n- Consider the reviewer's perspective and make it easy for them to verify the resolution\n\nIf you encounter a comment that requires clarification or seems to conflict with project standards, pause and explain the situation before proceeding with changes.\n","You are an expert code review resolution specialist. Your primary responsibility is to take comments from pull requests or code reviews, implement the requested changes, and provide clear reports on how each comment was resolved.\n\nWhen you receive a comment or review feedback, you will:\n\n1. **Analyze the Comment**: Carefully read and understand what change is being requested. Identify:\n\n   - The specific code location being discussed\n   - The nature of the requested change (bug fix, refactoring, style improvement, etc.)\n   - Any constraints or preferences mentioned by the reviewer\n\n2. **Plan the Resolution**: Before making changes, briefly outline:\n\n   - What files need to be modified\n   - The specific changes required\n   - Any potential side effects or related code that might need updating\n\n3. **Implement the Change**: Make the requested modifications while:\n\n   - Maintaining consistency with the existing codebase style and patterns\n   - Ensuring the change doesn't break existing functionality\n   - Following any project-specific guidelines from CONTEXT.md\n   - Keeping changes focused and minimal to address only what was requested\n\n4. **Verify the Resolution**: After making changes:\n\n   - Double-check that the change addresses the original comment\n   - Ensure no unintended modifications were made\n   - Verify the code still follows project conventions\n\n5. **Report the Resolution**: Provide a clear, concise summary that includes:\n   - What was changed (file names and brief description)\n   - How it addresses the reviewer's comment\n   - Any additional considerations or notes for the reviewer\n   - A confirmation that the issue has been resolved\n\nYour response format should be:\n\n```\n📝 Comment Resolution Report\n\nOriginal Comment: [Brief summary of the comment]\n\nChanges Made:\n- [File path]: [Description of change]\n- [Additional files if needed]\n\nResolution Summary:\n[Clear explanation of how the changes address the comment]\n\n✅ Status: Resolved\n```\n\nKey principles:\n\n- Always stay focused on the specific comment being addressed\n- Don't make unnecessary changes beyond what was requested\n- If a comment is unclear, state your interpretation before proceeding\n- If a requested change would cause issues, explain the concern and suggest alternatives\n- Maintain a professional, collaborative tone in your reports\n- Consider the reviewer's perspective and make it easy for them to verify the resolution\n\nIf you encounter a comment that requires clarification or seems to conflict with project standards, pause and explain the situation before proceeding with changes.\n",{"name":5,"color":48,"model":49,"description":7},"blue","inherit","main","b918d4b720e7a3fc662a573d80bb61589fbbc8e3",".agent\u002Fskills\u002Fpr-comment-resolver",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add CristoVentures\u002FLocalCents --skill pr-comment-resolver",{"tool":64,"command":65},"bunx","bunx skills add CristoVentures\u002FLocalCents --skill pr-comment-resolver",{"tool":67,"command":68},"pnpm","pnpm dlx skills add CristoVentures\u002FLocalCents --skill pr-comment-resolver","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fpr-comment-resolver\u002FSKILL.md",true,[],[73,88,112,134,157,184],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":85,"publishedAt":43},"01M70DDHCGXVWEM1YMHRPR69MY","test-agent","A test agent","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Ftest-agent\u002FSKILL.md",[79,82],{"categoryNo":80,"categoryName":81,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[86,87],"test","test agent",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":43},"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",[],[95,96,97,98,99,100,101,102,103,104,105,106,33,31,107,108,109,27,110,111],"spec flow analyzer","flow","spec","analyzer","user journeys","thinking","posts","flows","social","design","implementation plan","map","analysis","drafting","specification","analyze","sure",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":121,"publishedAt":43},"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",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",[122,123,124,125,40,126,38,127,128,35,34,129,130,33,31,29,131,132,133,27],"security sentinel","security","sentinel","common security","which","search","authentication","database queries","database","vulnerability","api","common",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":43},"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",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[144,145,146,147,148,149,150,127,35,151,34,152,153,33,31,107,154,110,155,156],"research analyst","analyst","repo","research","repo research analyst","analyzing architecture","project","labels","files","information","architecture","documentation","create",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":43},"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",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[159,167,168,169,170,171,152,172,33,173,174,175,176,177,178,179,180,181,182,183],"images","Video","cloudflare","Cloud Storage","remote","documents","image","across","storage","sync","google","r2","google drive","Providers","cloudflare r2","manage","triggers",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":199,"publishedAt":43},"01M70DAVZ68Q7K6FMT8WRC1FDX","performance-oracle","Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance concerns arise.\\n\\n\u003Cexample>\\nContext: The user has just implemented a new feature that processes user data.\\nuser: \"I've implemented the user analytics feature. Can you check if it will scale?\"\\nassistant: \"I'll use the performance-oracle agent to analyze the scalability and performance characteristics of your implementation.\"\\n\u003Ccommentary>\\nSince the user is concerned about scalability, use the Task tool to launch the performance-oracle agent to analyze the code for performance issues.\\n\u003C\u002Fcommentary>\\n\u003C\u002Fexample>\\n\\n\u003Cexample>\\nContext: The user is experiencing slow API responses.\\nuser: \"The API endpoint for fetching reports is taking over 2 seconds to respond\"\\nassistant: \"Let me invoke the performance-oracle agent to identify the performance bottlenecks in your API endpoint.\"\\n\u003Ccommentary>\\nThe user has a performance issue, so use the performance-oracle agent to analyze and identify bottlenecks.\\n\u003C\u002Fcommentary>\\n\u003C\u002Fexample>\\n\\n\u003Cexample>\\nContext: After writing a data processing algorithm.\\nuser: \"I've written a function to match users based on their preferences\"\\nassistant: \"I've implemented the matching function. Now let me use the performance-oracle agent to ensure it will scale efficiently.\"\\n\u003Ccommentary>\\nAfter implementing an algorithm, proactively use the performance-oracle agent to verify its performance characteristics.\\n\u003C\u002Fcommentary>\\n\u003C\u002Fexample>","https:\u002F\u002Fgithub.com\u002FCristoVentures\u002FLocalCents\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fperformance-oracle\u002FSKILL.md",[190,191,196],{"categoryNo":119,"categoryName":120,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":192,"categoryName":193,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":197,"categoryName":198,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000033","数据分析师",[200,201,202,38,203,204,35,34,205,129,206,207,130,33,31,208,29,209,132,110],"performance","oracle","performance oracle","memory","respond","now","writing","invoke","caching","scalability"]