[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736P88F9D2DBVFH5EQKDCQ5":3,"skill-same:01M736P88F9D2DBVFH5EQKDCQ5":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M736P88F9D2DBVFH5EQKDCQ5","agent-designer",null,"Agent Designer - Multi-Agent System Architecture","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fagent-designer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"agent-designer\"\ndescription: \"Agent Designer - Multi-Agent System Architecture\"\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","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fagent-designer","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill agent-designer",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill agent-designer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill agent-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fagent-designer\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","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\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]