@agentskillkit/agent-skills 1.0.1 → 3.2.1

package/.agent/workflows/agent.md

@@ -0,0 +1,77 @@
+---
+description: Launch interactive Agent Smart CLI. Learn patterns, recall violations, view stats, audit, and watch files.
+---
+
+# /agent - Interactive CLI Interface
+
+$ARGUMENTS
+
+---
+
+## Purpose
+
+Launch the **Agent Skill Kit Smart CLI** - an interactive terminal interface for managing learned patterns and memory.
+
+---
+
+## 🤖 Meta-Agents Integration
+
+| Phase | Agent | Action |
+| ----- | ----- | ------ |
+| **Pattern Learning** | `learner` | Store and recall anti-patterns |
+| **Audit** | `assessor` | Evaluate code compliance |
+
+---
+
+## 🔴 MANDATORY: Launch Protocol
+
+### Step 1: Run Interactive CLI
+// turbo
+```bash
+agent
+```
+
+---
+
+## Features
+
+| Menu Option | Description | Icon |
+|-------------|-------------|------|
+| **Learn** | Teach a new anti-pattern | ◆ |
+| **Recall** | Scan code for violations | ◇ |
+| **Stats** | View statistics & hit counts | ▣ |
+| **Audit** | Run compliance check | ▲ |
+| **Watch** | Real-time file monitoring | ○ |
+| **Exit** | Close the CLI | × |
+
+---
+
+## Examples
+
+```
+/agent              # Open main menu
+/agent learn        # Jump to Learn flow
+/agent recall       # Jump to Recall flow
+/agent stats        # View statistics
+```
+
+---
+
+## Keyboard Shortcuts
+
+| Key | Action |
+|-----|--------|
+| **↑/↓** | Navigate menu |
+| **Enter** | Select option |
+| **ESC** | Cancel / Go back |
+| **Ctrl+C** | Exit immediately |
+
+---
+
+## 🔗 Related Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/think` | Brainstorm before learning patterns |
+| `/validate` | Run full test suite |
+| `/diagnose` | Debug pattern detection issues |

package/.agent/workflows/alert.md

@@ -0,0 +1,333 @@
+---
+description: Configure alert rules and test incident response. Slack/PagerDuty integration with runbook automation.
+---
+
+# Alert Configuration Workflow
+
+Configure alert rules, test notifications, and setup incident response procedures.
+
+## 🎯 Purpose
+
+This workflow configures:
+
+- Custom alert rules for your application
+- Notification channels (Slack, PagerDuty, email)
+- Alert thresholds based on your SLAs
+- Runbook templates
+- Test alert delivery
+
+## 🤖 Meta-Agents Integration
+
+| Phase | Agent | Action |
+| ----- | ----- | ------ |
+| **Alert Analysis** | `learner` | Learn from past incident patterns |
+| **Threshold Tuning** | `assessor` | Evaluate alert sensitivity vs noise |
+| **Response Planning** | `orchestrator` | Coordinate multi-team response |
+
+```
+Flow:
+configure alerts → learner.analyze(past_incidents)
+       ↓
+assessor.tune(thresholds) → reduce noise
+       ↓
+incident? → orchestrator.coordinate(runbook)
+```
+
+---
+
+## 🔗 Chain: monitoring-production
+
+**Primary Skill:** `observability`
+
+**Coordinates with:** `observability`, `observability`, `observability`
+
+## 📖 Usage
+
+```bash
+/alert <configuration>
+```
+
+### Examples
+
+```bash
+# Configure standard alerts
+/alert configure for production
+
+# High-traffic scenario
+/alert configure for high-traffic (10K+ users)
+
+# Custom thresholds
+/alert configure with thresholds:
+- Error rate: 0.5%
+- Latency p95: 300ms
+- CPU: 80%
+
+# Test existing alerts
+/alert test all notifications
+```
+
+## 🔄 Workflow Steps
+
+This workflow automatically:
+
+1. **Analyze Application**
+   - Detect service type (API, web app, microservice)
+   - Review current traffic patterns
+   - Identify critical endpoints
+
+2. **Configure Alert Rules**
+   - Error rate alerts
+   - Latency alerts
+   - Infrastructure alerts (CPU, memory, disk)
+   - Custom business metric alerts
+   - Health check alerts
+
+3. **Setup Notification Channels**
+   - Slack webhook configuration
+   - PagerDuty integration
+   - Email notifications
+   - SMS (via PagerDuty)
+
+4. **Test Alert Delivery**
+   - Send test alerts to Slack
+   - Verify PagerDuty routing
+   - Check escalation policies
+
+5. **Generate Runbooks**
+   - Create playbooks for each alert
+   - Document investigation steps
+   - Define escalation procedures
+
+## 🎨 Alert Types
+
+### Application Alerts (P0 - Critical)
+
+```yaml
+- High Error Rate (>1%)
+- API Down (health check failed)
+- Database Connection Failed
+- Authentication Service Down
+```
+
+### Performance Alerts (P1 - High)
+
+```yaml
+- High Latency (p95 >500ms)
+- Slow Database Queries (>1s)
+- High Memory Usage (>90%)
+- Cache Miss Rate High (>30%)
+```
+
+### Infrastructure Alerts (P2 - Medium)
+
+```yaml
+- CPU Usage High (>80%)
+- Disk Usage High (>85%)
+- High Network Latency
+- SSL Certificate Expiring
+```
+
+## ✅ Success Criteria
+
+After running `/alert`, you will have:
+
+✓ **Alert Rules** - Configured in your monitoring platform
+✓ **Slack Integration** - Test alert delivered successfully
+✓ **PagerDuty Integration** - On-call routing configured
+✓ **Runbooks** - Documentation for each alert type
+✓ **Escalation Policy** - Clear escalation path defined
+✓ **Alert Testing** - All channels verified working
+
+## 📊 Recommended Thresholds
+
+### By Service Type
+
+**API Services:**
+
+```yaml
+error_rate: >0.5%
+latency_p95: >200ms
+latency_p99: >500ms
+```
+
+**Web Applications:**
+
+```yaml
+error_rate: >1%
+latency_p95: >300ms
+page_load_time: >3s
+```
+
+**Background Jobs:**
+
+```yaml
+queue_length: >1000
+processing_time: >30
+failure_rate: >5
+```
+
+### By Environment
+
+| Environment | Error Threshold | Latency Threshold |
+| ----------- | --------------- | ----------------- |
+| Development | N/A (no alerts) | N/A               |
+| Staging     | >5%             | >1000ms           |
+| Production  | >0.5%           | >200ms            |
+
+## 🔍 Notification Routing
+
+### Severity-Based Routing
+
+| Severity          | Notify               | Escalate After |
+| ----------------- | -------------------- | -------------- |
+| **Critical (P0)** | Slack + PagerDuty    | 15 minutes     |
+| **High (P1)**     | Slack only           | 30 minutes     |
+| **Medium (P2)**   | Slack (low-priority) | Never          |
+
+### Time-Based Routing
+
+**Business Hours (9am-6pm):**
+
+- All alerts → Slack engineering channel
+- P0 alerts → Page on-call engineer
+
+**Off Hours (6pm-9am, weekends):**
+
+- P0 alerts → Page on-call engineer immediately
+- P1 alerts → Slack only, review next day
+- P2 alerts → Batched daily summary
+
+## 💡 Tips
+
+**Alert Fatigue Prevention:**
+
+- Start with conservative thresholds, tighten gradually
+- Use anomaly detection (not just static thresholds)
+- Group related alerts (don't page for every instance)
+- Auto-resolve when issue clears
+- Weekly alert review and tuning
+
+**Good Alert Properties:**
+
+- **Actionable** - Clear what to do
+- **Specific** - Not "something is wrong"
+- **Timely** - Catch issues before users notice
+- **Documented** - Runbook exists
+
+**Bad Alerts (avoid):**
+
+- Alerts that fire constantly (tune thresholds)
+- Alerts with no runbook
+- Alerts that auto-resolve in <1 min
+- "Just FYI" alerts (use reports instead)
+
+## 📚 Example Output
+
+```bash
+You: "/alert configure for high-traffic"
+
+Agent: Analyzing application requirements...
+       ↓
+
+[1/4] 🎯 Alert Rules Configuration
+   ✅ High Error Rate (>0.5%)
+   ✅ Critical Latency (p95 >300ms)
+   ✅ Database Timeouts
+   ✅ Memory Usage (>85%)
+   ✅ Health Check Failures
+   ✅ Certificate Expiry (30 days)
+
+   Created: alerts.yml (15 rules)
+
+[2/4] 📢 Notification Channels
+   ✅ Slack webhook: https://hooks.slack.com/...
+   ✅ Channel: #oncall
+   ✅ PagerDuty service: production-alerts
+   ✅ Escalation: on-call → manager (15min)
+   ✅ Email: oncall@example.com
+
+[3/4] 🧪 Test Alerts
+   ✅ Sent test alert to Slack ✓
+   ✅ Verified webhook delivery
+   ✅ PagerDuty integration working
+   ✅ Escalation policy tested
+
+[4/4] 📖 Runbooks Generated
+   ✅ docs/runbooks/high-error-rate.md
+   ✅ docs/runbooks/high-latency.md
+   ✅ docs/runbooks/database-timeout.md
+   ✅ docs/runbooks/memory-leak.md
+   ✅ docs/runbooks/health-check-failure.md
+   ✅ Post-mortem template
+
+✅ Alerting configured!
+
+📊 Alert Dashboard: https://app.datadoghq.com/monitors
+🔔 Slack channel: #oncall
+📞 PagerDuty: https://example.pagerduty.com
+
+Next steps:
+1. Review alerts.yml and adjust thresholds
+2. Add team members to PagerDuty rotation
+3. Test alerts in staging first
+4. Update runbooks with team-specific procedures
+```
+
+## 🚨 Alert Rule Examples
+
+### High Error Rate
+
+```yaml
+name: HighErrorRate
+condition: |
+  (sum(rate(http_errors_total[5m])) / 
+   sum(rate(http_requests_total[5m]))) > 0.005
+severity: critical
+description: Error rate exceeded 0.5% in last 5 minutes
+notify:
+  - slack: "#oncall"
+  - pagerduty: "production-alerts"
+runbook: docs/runbooks/high-error-rate.md
+```
+
+### High Latency
+
+```yaml
+name: HighLatency
+condition: |
+  histogram_quantile(0.95, 
+    http_request_duration_ms_bucket) > 300
+severity: high
+description: p95 latency above 300ms
+notify:
+  - slack: "#engineering"
+runbook: docs/runbooks/high-latency.md
+```
+
+### Database Connection Pool Exhausted
+
+```yaml
+name: DatabasePoolExhausted
+condition: |
+  db_connection_pool_active / 
+  db_connection_pool_max > 0.9
+severity: critical
+description: Database connection pool at 90%+ capacity
+notify:
+  - slack: "#oncall"
+  - pagerduty: "production-alerts"
+runbook: docs/runbooks/database-pool.md
+```
+
+## 🔗 Related Workflows
+
+- `/monitor` - Setup full monitoring stack first
+- `/diagnose` - Investigate when alerts fire
+- `/launch` - Deploy with alerts pre-configured
+
+---
+
+**Version:** 1.0.0  
+**Chain:** monitoring-production (observability skill)  
+**Added:** v3.4.0 (FAANG upgrade)
+

package/.agent/workflows/api.md

@@ -0,0 +1,209 @@
+---
+description: REST/GraphQL/tRPC API builder with OpenAPI docs, Prisma ORM, and comprehensive testing
+---
+
+# API Development Workflow
+
+Build production-ready APIs with comprehensive design, implementation, and testing.
+
+## 🎯 Purpose
+
+This workflow uses the **api-development** chain to create well-architected APIs with:
+
+- RESTful or GraphQL design
+- Database schema design
+- API testing automation
+- Security validation
+- Best practices enforcement
+
+## 🤖 Meta-Agents Integration
+
+| Phase | Agent | Action |
+| ----- | ----- | ------ |
+| **Pre-Build** | `assessor` | Evaluate API complexity and risk |
+| **Pre-Build** | `recovery` | Save existing API state |
+| **Conflict** | `critic` | Resolve REST vs GraphQL decisions |
+| **Post-Build** | `learner` | Learn API patterns for reuse |
+
+```
+Flow:
+assessor.evaluate(api_scope) → risk level
+       ↓
+recovery.save(existing_api) → backup
+       ↓
+build → test → learner.log(patterns)
+```
+
+---
+
+## 🔗 Chain: api-development
+
+**Skills Loaded (5):**
+
+- `api-architect` - REST/GraphQL/tRPC design patterns
+- `data-modeler` - Database schema and optimization
+- `nodejs-pro` - Node.js best practices and async patterns
+- `test-architect` - API testing strategies (unit, integration, E2E)
+- `security-scanner` - API security validation (OWASP)
+
+## 📖 Usage
+
+```bash
+/api <description>
+```
+
+### Examples
+
+```bash
+# REST API
+/api user management REST API with Express and Prisma
+
+# GraphQL API
+/api GraphQL API for e-commerce with Apollo Server
+
+# Microservice
+/api payments microservice with Stripe integration
+
+# Full specification
+/api blog API
+Requirements:
+- RESTful design
+- PostgreSQL with Prisma
+- JWT authentication
+- Rate limiting
+- Comprehensive tests
+```
+
+## 🔄 Workflow Steps
+
+This workflow automatically:
+
+1. **API Design**
+   - Define endpoints/schema
+   - Choose RESTful or GraphQL
+   - Design request/response formats
+
+2. **Database Schema**
+   - Design data model
+   - Define relationships
+   - Plan migrations
+
+3. **Implementation**
+   - Implement routes/resolvers
+   - Add validation
+   - Error handling
+
+4. **Testing**
+   - Unit tests for logic
+   - Integration tests for endpoints
+   - E2E tests for flows
+
+5. **Security**
+   - Authentication/authorization
+   - Input validation
+   - Rate limiting
+   - OWASP checks
+
+6. **Documentation**
+   - API documentation
+   - OpenAPI/GraphQL schema
+   - Usage examples
+
+## 🎨 Supported Patterns
+
+### REST APIs
+
+- Express.js, Fastify, NestJS
+- OpenAPI/Swagger
+- Versioning strategies
+
+### GraphQL
+
+- Apollo Server, GraphQL Yoga
+- Schema-first or code-first
+- Resolvers, dataloaders
+
+### tRPC
+
+- Type-safe APIs
+- End-to-end typing
+- Next.js integration
+
+### Real-time
+
+- WebSockets
+- Server-Sent Events
+- Polling strategies
+
+## ✅ Best Practices Applied
+
+✓ **Design First** - Plan before implementation
+✓ **Type Safety** - TypeScript throughout
+✓ **Validation** - Input/output validation
+✓ **Error Handling** - Consistent error responses
+✓ **Testing** - Comprehensive test coverage
+✓ **Security** - OWASP Top 10 compliance
+✓ **Documentation** - Auto-generated docs
+✓ **Performance** - Caching, pagination
+
+## 🔍 Related Workflows
+
+- `/build` - Full-stack app with API + frontend
+- `/inspect` - Security audit for existing API
+- `/validate` - Run API tests
+- `/launch` - Deploy API to production
+
+## 💡 Tips
+
+**When to use `/api`:**
+
+- API-only projects
+- Microservices
+- Backend services
+- Mobile app backends
+
+**When to use `/build` instead:**
+
+- Full-stack applications
+- API + frontend together
+- Monolithic apps
+
+## 📚 Example Output
+
+```bash
+You: "/api user management REST API with Express and Prisma"
+
+Agent: Loading api-development chain
+       ↓
+Skills: api-architect, data-modeler, nodejs-pro, test-architect, security-scanner
+       ↓
+
+Creates:
+✓ src/
+  ├── routes/
+  │   ├── auth.routes.ts
+  │   ├── users.routes.ts
+  │   └── index.ts
+  ├── controllers/
+  │   ├── auth.controller.ts
+  │   └── users.controller.ts
+  ├── services/
+  │   └── user.service.ts
+  ├── middleware/
+  │   ├── auth.middleware.ts
+  │   └── validation.middleware.ts
+  └── tests/
+      ├── auth.test.ts
+      └── users.test.ts
+✓ prisma/
+  └── schema.prisma
+✓ API documentation (OpenAPI)
+✓ Postman collection
+✓ README with setup instructions
+```
+
+---
+
+**Version:** 1.0.0  
+**Chain:** api-development  
+**Added:** v3.3.0