[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BF3X9XZDD4MPRAQ1T4GH9":3,"skill-same:01M75BF3X9XZDD4MPRAQ1T4GH9":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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75BF3X9XZDD4MPRAQ1T4GH9","agent-designer",null,"Use when the user asks to design multi-agent systems, create agent architectures, define agent communication patterns, or build autonomous agent workflows.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fagent-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: \"agent-designer\"\ndescription: \"Use when the user asks to design multi-agent systems, create agent architectures, define agent communication patterns, or build autonomous agent workflows.\"\n---\n\n# Agent Designer - Multi-Agent System Architecture\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Tags:** AI agents, architecture, system design, orchestration, multi-agent systems\n\n## Overview\n\nAgent Designer is a comprehensive toolkit for designing, architecting, and evaluating multi-agent systems. It provides structured approaches to agent architecture patterns, tool design principles, communication strategies, and performance evaluation frameworks for building robust, scalable AI agent systems.\n\n## Core Capabilities\n\n### 1. Agent Architecture Patterns\n\n#### Single Agent Pattern\n- **Use Case:** Simple, focused tasks with clear boundaries\n- **Pros:** Minimal complexity, easy debugging, predictable behavior\n- **Cons:** Limited scalability, single point of failure\n- **Implementation:** Direct user-agent interaction with comprehensive tool access\n\n#### Supervisor Pattern\n- **Use Case:** Hierarchical task decomposition with centralized control\n- **Architecture:** One supervisor agent coordinating multiple specialist agents\n- **Pros:** Clear command structure, centralized decision making\n- **Cons:** Supervisor bottleneck, complex coordination logic\n- **Implementation:** Supervisor receives tasks, delegates to specialists, aggregates results\n\n#### Swarm Pattern\n- **Use Case:** Distributed problem solving with peer-to-peer collaboration\n- **Architecture:** Multiple autonomous agents with shared objectives\n- **Pros:** High parallelism, fault tolerance, emergent intelligence\n- **Cons:** Complex coordination, potential conflicts, harder to predict\n- **Implementation:** Agent discovery, consensus mechanisms, distributed task allocation\n\n#### Hierarchical Pattern\n- **Use Case:** Complex systems with multiple organizational layers\n- **Architecture:** Tree structure with managers and workers at different levels\n- **Pros:** Natural organizational mapping, clear responsibilities\n- **Cons:** Communication overhead, potential bottlenecks at each level\n- **Implementation:** Multi-level delegation with feedback loops\n\n#### Pipeline Pattern\n- **Use Case:** Sequential processing with specialized stages\n- **Architecture:** Agents arranged in processing pipeline\n- **Pros:** Clear data flow, specialized optimization per stage\n- **Cons:** Sequential bottlenecks, rigid processing order\n- **Implementation:** Message queues between stages, state handoffs\n\n### 2. Agent Role Definition\n\n#### Role Specification Framework\n- **Identity:** Name, purpose statement, core competencies\n- **Responsibilities:** Primary tasks, decision boundaries, success criteria\n- **Capabilities:** Required tools, knowledge domains, processing limits\n- **Interfaces:** Input\u002Foutput formats, communication protocols\n- **Constraints:** Security boundaries, resource limits, operational guidelines\n\n#### Common Agent Archetypes\n\n**Coordinator Agent**\n- Orchestrates multi-agent workflows\n- Makes high-level decisions and resource allocation\n- Monitors system health and performance\n- Handles escalations and conflict resolution\n\n**Specialist Agent**\n- Deep expertise in specific domain (code, data, research)\n- Optimized tools and knowledge for specialized tasks\n- High-quality output within narrow scope\n- Clear handoff protocols for out-of-scope requests\n\n**Interface Agent**\n- Handles external interactions (users, APIs, systems)\n- Protocol translation and format conversion\n- Authentication and authorization management\n- User experience optimization\n\n**Monitor Agent**\n- System health monitoring and alerting\n- Performance metrics collection and analysis\n- Anomaly detection and reporting\n- Compliance and audit trail maintenance\n\n### 3. Tool Design Principles\n\n#### Schema Design\n- **Input Validation:** Strong typing, required vs optional parameters\n- **Output Consistency:** Standardized response formats, error handling\n- **Documentation:** Clear descriptions, usage examples, edge cases\n- **Versioning:** Backward compatibility, migration paths\n\n#### Error Handling Patterns\n- **Graceful Degradation:** Partial functionality when dependencies fail\n- **Retry Logic:** Exponential backoff, circuit breakers, max attempts\n- **Error Propagation:** Structured error responses, error classification\n- **Recovery Strategies:** Fallback methods, alternative approaches\n\n#### Idempotency Requirements\n- **Safe Operations:** Read operations with no side effects\n- **Idempotent Writes:** Same operation can be safely repeated\n- **State Management:** Version tracking, conflict resolution\n- **Atomicity:** All-or-nothing operation completion\n\n### 4. Communication Patterns\n\n#### Message Passing\n- **Asynchronous Messaging:** Decoupled agents, message queues\n- **Message Format:** Structured payloads with metadata\n- **Delivery Guarantees:** At-least-once, exactly-once semantics\n- **Routing:** Direct messaging, publish-subscribe, broadcast\n\n#### Shared State\n- **State Stores:** Centralized data repositories\n- **Consistency Models:** Strong, eventual, weak consistency\n- **Access Patterns:** Read-heavy, write-heavy, mixed workloads\n- **Conflict Resolution:** Last-writer-wins, merge strategies\n\n#### Event-Driven Architecture\n- **Event Sourcing:** Immutable event logs, state reconstruction\n- **Event Types:** Domain events, system events, integration events\n- **Event Processing:** Real-time, batch, stream processing\n- **Event Schema:** Versioned event formats, backward compatibility\n\n### 5. Guardrails and Safety\n\n#### Input Validation\n- **Schema Enforcement:** Required fields, type checking, format validation\n- **Content Filtering:** Harmful content detection, PII scrubbing\n- **Rate Limiting:** Request throttling, resource quotas\n- **Authentication:** Identity verification, authorization checks\n\n#### Output Filtering\n- **Content Moderation:** Harmful content removal, quality checks\n- **Consistency Validation:** Logic checks, constraint verification\n- **Formatting:** Standardized output formats, clean presentation\n- **Audit Logging:** Decision trails, compliance records\n\n#### Human-in-the-Loop\n- **Approval Workflows:** Critical decision checkpoints\n- **Escalation Triggers:** Confidence thresholds, risk assessment\n- **Override Mechanisms:** Human judgment precedence\n- **Feedback Loops:** Human corrections improve system behavior\n\n### 6. Evaluation Frameworks\n\n#### Task Completion Metrics\n- **Success Rate:** Percentage of tasks completed successfully\n- **Partial Completion:** Progress measurement for complex tasks\n- **Task Classification:** Success criteria by task type\n- **Failure Analysis:** Root cause identification and categorization\n\n#### Quality Assessment\n- **Output Quality:** Accuracy, relevance, completeness measures\n- **Consistency:** Response variability across similar inputs\n- **Coherence:** Logical flow and internal consistency\n- **User Satisfaction:** Feedback scores, usage patterns\n\n#### Cost Analysis\n- **Token Usage:** Input\u002Foutput token consumption per task\n- **API Costs:** External service usage and charges\n- **Compute Resources:** CPU, memory, storage utilization\n- **Time-to-Value:** Cost per successful task completion\n\n#### Latency Distribution\n- **Response Time:** End-to-end task completion time\n- **Processing Stages:** Bottleneck identification per stage\n- **Queue Times:** Wait times in processing pipelines\n- **Resource Contention:** Impact of concurrent operations\n\n### 7. Orchestration Strategies\n\n#### Centralized Orchestration\n- **Workflow Engine:** Central coordinator manages all agents\n- **State Management:** Centralized workflow state tracking\n- **Decision Logic:** Complex routing and branching rules\n- **Monitoring:** Comprehensive visibility into all operations\n\n#### Decentralized Orchestration\n- **Peer-to-Peer:** Agents coordinate directly with each other\n- **Service Discovery:** Dynamic agent registration and lookup\n- **Consensus Protocols:** Distributed decision making\n- **Fault Tolerance:** No single point of failure\n\n#### Hybrid Approaches\n- **Domain Boundaries:** Centralized within domains, federated across\n- **Hierarchical Coordination:** Multiple orchestration levels\n- **Context-Dependent:** Strategy selection based on task type\n- **Load Balancing:** Distribute coordination responsibility\n\n### 8. Memory Patterns\n\n#### Short-Term Memory\n- **Context Windows:** Working memory for current tasks\n- **Session State:** Temporary data for ongoing interactions\n- **Cache Management:** Performance optimization strategies\n- **Memory Pressure:** Handling capacity constraints\n\n#### Long-Term Memory\n- **Persistent Storage:** Durable data across sessions\n- **Knowledge Base:** Accumulated domain knowledge\n- **Experience Replay:** Learning from past interactions\n- **Memory Consolidation:** Transferring from short to long-term\n\n#### Shared Memory\n- **Collaborative Knowledge:** Shared learning across agents\n- **Synchronization:** Consistency maintenance strategies\n- **Access Control:** Permission-based memory access\n- **Memory Partitioning:** Isolation between agent groups\n\n### 9. Scaling Considerations\n\n#### Horizontal Scaling\n- **Agent Replication:** Multiple instances of same agent type\n- **Load Distribution:** Request routing across agent instances\n- **Resource Pooling:** Shared compute and storage resources\n- **Geographic Distribution:** Multi-region deployments\n\n#### Vertical Scaling\n- **Capability Enhancement:** More powerful individual agents\n- **Tool Expansion:** Broader tool access per agent\n- **Context Expansion:** Larger working memory capacity\n- **Processing Power:** Higher throughput per agent\n\n#### Performance Optimization\n- **Caching Strategies:** Response caching, tool result caching\n- **Parallel Processing:** Concurrent task execution\n- **Resource Optimization:** Efficient resource utilization\n- **Bottleneck Elimination:** Systematic performance tuning\n\n### 10. Failure Handling\n\n#### Retry Mechanisms\n- **Exponential Backoff:** Increasing delays between retries\n- **Jitter:** Random delay variation to prevent thundering herd\n- **Maximum Attempts:** Bounded retry behavior\n- **Retry Conditions:** Transient vs permanent failure classification\n\n#### Fallback Strategies\n- **Graceful Degradation:** Reduced functionality when systems fail\n- **Alternative Approaches:** Different methods for same goals\n- **Default Responses:** Safe fallback behaviors\n- **User Communication:** Clear failure messaging\n\n#### Circuit Breakers\n- **Failure Detection:** Monitoring failure rates and response times\n- **State Management:** Open, closed, half-open circuit states\n- **Recovery Testing:** Gradual return to normal operation\n- **Cascading Failure Prevention:** Protecting upstream systems\n\n## Implementation Guidelines\n\n### Architecture Decision Process\n1. **Requirements Analysis:** Understand system goals, constraints, scale\n2. **Pattern Selection:** Choose appropriate architecture pattern\n3. **Agent Design:** Define roles, responsibilities, interfaces\n4. **Tool Architecture:** Design tool schemas and error handling\n5. **Communication Design:** Select message patterns and protocols\n6. **Safety Implementation:** Build guardrails and validation\n7. **Evaluation Planning:** Define success metrics and monitoring\n8. **Deployment Strategy:** Plan scaling and failure handling\n\n### Quality Assurance\n- **Testing Strategy:** Unit, integration, and system testing approaches\n- **Monitoring:** Real-time system health and performance tracking\n- **Documentation:** Architecture documentation and runbooks\n- **Security Review:** Threat modeling and security assessments\n\n### Continuous Improvement\n- **Performance Monitoring:** Ongoing system performance analysis\n- **User Feedback:** Incorporating user experience improvements\n- **A\u002FB Testing:** Controlled experiments for system improvements\n- **Knowledge Base Updates:** Continuous learning and adaptation\n\nThis skill provides the foundation for designing robust, scalable multi-agent systems that can handle complex tasks while maintaining safety, reliability, and performance at scale.","# Agent Designer - Multi-Agent System Architecture\n\n**Tier:** POWERFUL  \n**Category:** Engineering  \n**Tags:** AI agents, architecture, system design, orchestration, multi-agent systems\n\n## Overview\n\nAgent Designer is a comprehensive toolkit for designing, architecting, and evaluating multi-agent systems. It provides structured approaches to agent architecture patterns, tool design principles, communication strategies, and performance evaluation frameworks for building robust, scalable AI agent systems.\n\n## Core Capabilities\n\n### 1. Agent Architecture Patterns\n\n#### Single Agent Pattern\n- **Use Case:** Simple, focused tasks with clear boundaries\n- **Pros:** Minimal complexity, easy debugging, predictable behavior\n- **Cons:** Limited scalability, single point of failure\n- **Implementation:** Direct user-agent interaction with comprehensive tool access\n\n#### Supervisor Pattern\n- **Use Case:** Hierarchical task decomposition with centralized control\n- **Architecture:** One supervisor agent coordinating multiple specialist agents\n- **Pros:** Clear command structure, centralized decision making\n- **Cons:** Supervisor bottleneck, complex coordination logic\n- **Implementation:** Supervisor receives tasks, delegates to specialists, aggregates results\n\n#### Swarm Pattern\n- **Use Case:** Distributed problem solving with peer-to-peer collaboration\n- **Architecture:** Multiple autonomous agents with shared objectives\n- **Pros:** High parallelism, fault tolerance, emergent intelligence\n- **Cons:** Complex coordination, potential conflicts, harder to predict\n- **Implementation:** Agent discovery, consensus mechanisms, distributed task allocation\n\n#### Hierarchical Pattern\n- **Use Case:** Complex systems with multiple organizational layers\n- **Architecture:** Tree structure with managers and workers at different levels\n- **Pros:** Natural organizational mapping, clear responsibilities\n- **Cons:** Communication overhead, potential bottlenecks at each level\n- **Implementation:** Multi-level delegation with feedback loops\n\n#### Pipeline Pattern\n- **Use Case:** Sequential processing with specialized stages\n- **Architecture:** Agents arranged in processing pipeline\n- **Pros:** Clear data flow, specialized optimization per stage\n- **Cons:** Sequential bottlenecks, rigid processing order\n- **Implementation:** Message queues between stages, state handoffs\n\n### 2. Agent Role Definition\n\n#### Role Specification Framework\n- **Identity:** Name, purpose statement, core competencies\n- **Responsibilities:** Primary tasks, decision boundaries, success criteria\n- **Capabilities:** Required tools, knowledge domains, processing limits\n- **Interfaces:** Input\u002Foutput formats, communication protocols\n- **Constraints:** Security boundaries, resource limits, operational guidelines\n\n#### Common Agent Archetypes\n\n**Coordinator Agent**\n- Orchestrates multi-agent workflows\n- Makes high-level decisions and resource allocation\n- Monitors system health and performance\n- Handles escalations and conflict resolution\n\n**Specialist Agent**\n- Deep expertise in specific domain (code, data, research)\n- Optimized tools and knowledge for specialized tasks\n- High-quality output within narrow scope\n- Clear handoff protocols for out-of-scope requests\n\n**Interface Agent**\n- Handles external interactions (users, APIs, systems)\n- Protocol translation and format conversion\n- Authentication and authorization management\n- User experience optimization\n\n**Monitor Agent**\n- System health monitoring and alerting\n- Performance metrics collection and analysis\n- Anomaly detection and reporting\n- Compliance and audit trail maintenance\n\n### 3. Tool Design Principles\n\n#### Schema Design\n- **Input Validation:** Strong typing, required vs optional parameters\n- **Output Consistency:** Standardized response formats, error handling\n- **Documentation:** Clear descriptions, usage examples, edge cases\n- **Versioning:** Backward compatibility, migration paths\n\n#### Error Handling Patterns\n- **Graceful Degradation:** Partial functionality when dependencies fail\n- **Retry Logic:** Exponential backoff, circuit breakers, max attempts\n- **Error Propagation:** Structured error responses, error classification\n- **Recovery Strategies:** Fallback methods, alternative approaches\n\n#### Idempotency Requirements\n- **Safe Operations:** Read operations with no side effects\n- **Idempotent Writes:** Same operation can be safely repeated\n- **State Management:** Version tracking, conflict resolution\n- **Atomicity:** All-or-nothing operation completion\n\n### 4. Communication Patterns\n\n#### Message Passing\n- **Asynchronous Messaging:** Decoupled agents, message queues\n- **Message Format:** Structured payloads with metadata\n- **Delivery Guarantees:** At-least-once, exactly-once semantics\n- **Routing:** Direct messaging, publish-subscribe, broadcast\n\n#### Shared State\n- **State Stores:** Centralized data repositories\n- **Consistency Models:** Strong, eventual, weak consistency\n- **Access Patterns:** Read-heavy, write-heavy, mixed workloads\n- **Conflict Resolution:** Last-writer-wins, merge strategies\n\n#### Event-Driven Architecture\n- **Event Sourcing:** Immutable event logs, state reconstruction\n- **Event Types:** Domain events, system events, integration events\n- **Event Processing:** Real-time, batch, stream processing\n- **Event Schema:** Versioned event formats, backward compatibility\n\n### 5. Guardrails and Safety\n\n#### Input Validation\n- **Schema Enforcement:** Required fields, type checking, format validation\n- **Content Filtering:** Harmful content detection, PII scrubbing\n- **Rate Limiting:** Request throttling, resource quotas\n- **Authentication:** Identity verification, authorization checks\n\n#### Output Filtering\n- **Content Moderation:** Harmful content removal, quality checks\n- **Consistency Validation:** Logic checks, constraint verification\n- **Formatting:** Standardized output formats, clean presentation\n- **Audit Logging:** Decision trails, compliance records\n\n#### Human-in-the-Loop\n- **Approval Workflows:** Critical decision checkpoints\n- **Escalation Triggers:** Confidence thresholds, risk assessment\n- **Override Mechanisms:** Human judgment precedence\n- **Feedback Loops:** Human corrections improve system behavior\n\n### 6. Evaluation Frameworks\n\n#### Task Completion Metrics\n- **Success Rate:** Percentage of tasks completed successfully\n- **Partial Completion:** Progress measurement for complex tasks\n- **Task Classification:** Success criteria by task type\n- **Failure Analysis:** Root cause identification and categorization\n\n#### Quality Assessment\n- **Output Quality:** Accuracy, relevance, completeness measures\n- **Consistency:** Response variability across similar inputs\n- **Coherence:** Logical flow and internal consistency\n- **User Satisfaction:** Feedback scores, usage patterns\n\n#### Cost Analysis\n- **Token Usage:** Input\u002Foutput token consumption per task\n- **API Costs:** External service usage and charges\n- **Compute Resources:** CPU, memory, storage utilization\n- **Time-to-Value:** Cost per successful task completion\n\n#### Latency Distribution\n- **Response Time:** End-to-end task completion time\n- **Processing Stages:** Bottleneck identification per stage\n- **Queue Times:** Wait times in processing pipelines\n- **Resource Contention:** Impact of concurrent operations\n\n### 7. Orchestration Strategies\n\n#### Centralized Orchestration\n- **Workflow Engine:** Central coordinator manages all agents\n- **State Management:** Centralized workflow state tracking\n- **Decision Logic:** Complex routing and branching rules\n- **Monitoring:** Comprehensive visibility into all operations\n\n#### Decentralized Orchestration\n- **Peer-to-Peer:** Agents coordinate directly with each other\n- **Service Discovery:** Dynamic agent registration and lookup\n- **Consensus Protocols:** Distributed decision making\n- **Fault Tolerance:** No single point of failure\n\n#### Hybrid Approaches\n- **Domain Boundaries:** Centralized within domains, federated across\n- **Hierarchical Coordination:** Multiple orchestration levels\n- **Context-Dependent:** Strategy selection based on task type\n- **Load Balancing:** Distribute coordination responsibility\n\n### 8. Memory Patterns\n\n#### Short-Term Memory\n- **Context Windows:** Working memory for current tasks\n- **Session State:** Temporary data for ongoing interactions\n- **Cache Management:** Performance optimization strategies\n- **Memory Pressure:** Handling capacity constraints\n\n#### Long-Term Memory\n- **Persistent Storage:** Durable data across sessions\n- **Knowledge Base:** Accumulated domain knowledge\n- **Experience Replay:** Learning from past interactions\n- **Memory Consolidation:** Transferring from short to long-term\n\n#### Shared Memory\n- **Collaborative Knowledge:** Shared learning across agents\n- **Synchronization:** Consistency maintenance strategies\n- **Access Control:** Permission-based memory access\n- **Memory Partitioning:** Isolation between agent groups\n\n### 9. Scaling Considerations\n\n#### Horizontal Scaling\n- **Agent Replication:** Multiple instances of same agent type\n- **Load Distribution:** Request routing across agent instances\n- **Resource Pooling:** Shared compute and storage resources\n- **Geographic Distribution:** Multi-region deployments\n\n#### Vertical Scaling\n- **Capability Enhancement:** More powerful individual agents\n- **Tool Expansion:** Broader tool access per agent\n- **Context Expansion:** Larger working memory capacity\n- **Processing Power:** Higher throughput per agent\n\n#### Performance Optimization\n- **Caching Strategies:** Response caching, tool result caching\n- **Parallel Processing:** Concurrent task execution\n- **Resource Optimization:** Efficient resource utilization\n- **Bottleneck Elimination:** Systematic performance tuning\n\n### 10. Failure Handling\n\n#### Retry Mechanisms\n- **Exponential Backoff:** Increasing delays between retries\n- **Jitter:** Random delay variation to prevent thundering herd\n- **Maximum Attempts:** Bounded retry behavior\n- **Retry Conditions:** Transient vs permanent failure classification\n\n#### Fallback Strategies\n- **Graceful Degradation:** Reduced functionality when systems fail\n- **Alternative Approaches:** Different methods for same goals\n- **Default Responses:** Safe fallback behaviors\n- **User Communication:** Clear failure messaging\n\n#### Circuit Breakers\n- **Failure Detection:** Monitoring failure rates and response times\n- **State Management:** Open, closed, half-open circuit states\n- **Recovery Testing:** Gradual return to normal operation\n- **Cascading Failure Prevention:** Protecting upstream systems\n\n## Implementation Guidelines\n\n### Architecture Decision Process\n1. **Requirements Analysis:** Understand system goals, constraints, scale\n2. **Pattern Selection:** Choose appropriate architecture pattern\n3. **Agent Design:** Define roles, responsibilities, interfaces\n4. **Tool Architecture:** Design tool schemas and error handling\n5. **Communication Design:** Select message patterns and protocols\n6. **Safety Implementation:** Build guardrails and validation\n7. **Evaluation Planning:** Define success metrics and monitoring\n8. **Deployment Strategy:** Plan scaling and failure handling\n\n### Quality Assurance\n- **Testing Strategy:** Unit, integration, and system testing approaches\n- **Monitoring:** Real-time system health and performance tracking\n- **Documentation:** Architecture documentation and runbooks\n- **Security Review:** Threat modeling and security assessments\n\n### Continuous Improvement\n- **Performance Monitoring:** Ongoing system performance analysis\n- **User Feedback:** Incorporating user experience improvements\n- **A\u002FB Testing:** Controlled experiments for system improvements\n- **Knowledge Base Updates:** Continuous learning and adaptation\n\nThis skill provides the foundation for designing robust, scalable multi-agent systems that can handle complex tasks while maintaining safety, reliability, and performance at scale.",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fagent-designer",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill agent-designer",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill agent-designer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill agent-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fagent-designer\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"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":53,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]