@zimezone/z-command 1.1.1 → 1.1.2

package/templates/skills/prometheus-configuration/SKILL.md

@@ -1,392 +0,0 @@
----
-name: prometheus-configuration
-description: Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.
----
-
-# Prometheus Configuration
-
-Complete guide to Prometheus setup, metric collection, scrape configuration, and recording rules.
-
-## Purpose
-
-Configure Prometheus for comprehensive metric collection, alerting, and monitoring of infrastructure and applications.
-
-## When to Use
-
-- Set up Prometheus monitoring
-- Configure metric scraping
-- Create recording rules
-- Design alert rules
-- Implement service discovery
-
-## Prometheus Architecture
-
-```
-┌──────────────┐
-│ Applications │ ← Instrumented with client libraries
-└──────┬───────┘
-       │ /metrics endpoint
-       ↓
-┌──────────────┐
-│  Prometheus  │ ← Scrapes metrics periodically
-│    Server    │
-└──────┬───────┘
-       │
-       ├─→ AlertManager (alerts)
-       ├─→ Grafana (visualization)
-       └─→ Long-term storage (Thanos/Cortex)
-```
-
-## Installation
-
-### Kubernetes with Helm
-
-```bash
-helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
-helm repo update
-
-helm install prometheus prometheus-community/kube-prometheus-stack \
-  --namespace monitoring \
-  --create-namespace \
-  --set prometheus.prometheusSpec.retention=30d \
-  --set prometheus.prometheusSpec.storageVolumeSize=50Gi
-```
-
-### Docker Compose
-
-```yaml
-version: '3.8'
-services:
-  prometheus:
-    image: prom/prometheus:latest
-    ports:
-      - "9090:9090"
-    volumes:
-      - ./prometheus.yml:/etc/prometheus/prometheus.yml
-      - prometheus-data:/prometheus
-    command:
-      - '--config.file=/etc/prometheus/prometheus.yml'
-      - '--storage.tsdb.path=/prometheus'
-      - '--storage.tsdb.retention.time=30d'
-
-volumes:
-  prometheus-data:
-```
-
-## Configuration File
-
-**prometheus.yml:**
-```yaml
-global:
-  scrape_interval: 15s
-  evaluation_interval: 15s
-  external_labels:
-    cluster: 'production'
-    region: 'us-west-2'
-
-# Alertmanager configuration
-alerting:
-  alertmanagers:
-    - static_configs:
-        - targets:
-          - alertmanager:9093
-
-# Load rules files
-rule_files:
-  - /etc/prometheus/rules/*.yml
-
-# Scrape configurations
-scrape_configs:
-  # Prometheus itself
-  - job_name: 'prometheus'
-    static_configs:
-      - targets: ['localhost:9090']
-
-  # Node exporters
-  - job_name: 'node-exporter'
-    static_configs:
-      - targets:
-        - 'node1:9100'
-        - 'node2:9100'
-        - 'node3:9100'
-    relabel_configs:
-      - source_labels: [__address__]
-        target_label: instance
-        regex: '([^:]+)(:[0-9]+)?'
-        replacement: '${1}'
-
-  # Kubernetes pods with annotations
-  - job_name: 'kubernetes-pods'
-    kubernetes_sd_configs:
-      - role: pod
-    relabel_configs:
-      - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_scrape]
-        action: keep
-        regex: true
-      - source_labels: [__meta_kubernetes_pod_annotation_prometheus_io_path]
-        action: replace
-        target_label: __metrics_path__
-        regex: (.+)
-      - source_labels: [__address__, __meta_kubernetes_pod_annotation_prometheus_io_port]
-        action: replace
-        regex: ([^:]+)(?::\d+)?;(\d+)
-        replacement: $1:$2
-        target_label: __address__
-      - source_labels: [__meta_kubernetes_namespace]
-        action: replace
-        target_label: namespace
-      - source_labels: [__meta_kubernetes_pod_name]
-        action: replace
-        target_label: pod
-
-  # Application metrics
-  - job_name: 'my-app'
-    static_configs:
-      - targets:
-        - 'app1.example.com:9090'
-        - 'app2.example.com:9090'
-    metrics_path: '/metrics'
-    scheme: 'https'
-    tls_config:
-      ca_file: /etc/prometheus/ca.crt
-      cert_file: /etc/prometheus/client.crt
-      key_file: /etc/prometheus/client.key
-```
-
-**Reference:** See `assets/prometheus.yml.template`
-
-## Scrape Configurations
-
-### Static Targets
-
-```yaml
-scrape_configs:
-  - job_name: 'static-targets'
-    static_configs:
-      - targets: ['host1:9100', 'host2:9100']
-        labels:
-          env: 'production'
-          region: 'us-west-2'
-```
-
-### File-based Service Discovery
-
-```yaml
-scrape_configs:
-  - job_name: 'file-sd'
-    file_sd_configs:
-      - files:
-        - /etc/prometheus/targets/*.json
-        - /etc/prometheus/targets/*.yml
-        refresh_interval: 5m
-```
-
-**targets/production.json:**
-```json
-[
-  {
-    "targets": ["app1:9090", "app2:9090"],
-    "labels": {
-      "env": "production",
-      "service": "api"
-    }
-  }
-]
-```
-
-### Kubernetes Service Discovery
-
-```yaml
-scrape_configs:
-  - job_name: 'kubernetes-services'
-    kubernetes_sd_configs:
-      - role: service
-    relabel_configs:
-      - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scrape]
-        action: keep
-        regex: true
-      - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_scheme]
-        action: replace
-        target_label: __scheme__
-        regex: (https?)
-      - source_labels: [__meta_kubernetes_service_annotation_prometheus_io_path]
-        action: replace
-        target_label: __metrics_path__
-        regex: (.+)
-```
-
-**Reference:** See `references/scrape-configs.md`
-
-## Recording Rules
-
-Create pre-computed metrics for frequently queried expressions:
-
-```yaml
-# /etc/prometheus/rules/recording_rules.yml
-groups:
-  - name: api_metrics
-    interval: 15s
-    rules:
-      # HTTP request rate per service
-      - record: job:http_requests:rate5m
-        expr: sum by (job) (rate(http_requests_total[5m]))
-
-      # Error rate percentage
-      - record: job:http_requests_errors:rate5m
-        expr: sum by (job) (rate(http_requests_total{status=~"5.."}[5m]))
-
-      - record: job:http_requests_error_rate:percentage
-        expr: |
-          (job:http_requests_errors:rate5m / job:http_requests:rate5m) * 100
-
-      # P95 latency
-      - record: job:http_request_duration:p95
-        expr: |
-          histogram_quantile(0.95,
-            sum by (job, le) (rate(http_request_duration_seconds_bucket[5m]))
-          )
-
-  - name: resource_metrics
-    interval: 30s
-    rules:
-      # CPU utilization percentage
-      - record: instance:node_cpu:utilization
-        expr: |
-          100 - (avg by (instance) (rate(node_cpu_seconds_total{mode="idle"}[5m])) * 100)
-
-      # Memory utilization percentage
-      - record: instance:node_memory:utilization
-        expr: |
-          100 - ((node_memory_MemAvailable_bytes / node_memory_MemTotal_bytes) * 100)
-
-      # Disk usage percentage
-      - record: instance:node_disk:utilization
-        expr: |
-          100 - ((node_filesystem_avail_bytes / node_filesystem_size_bytes) * 100)
-```
-
-**Reference:** See `references/recording-rules.md`
-
-## Alert Rules
-
-```yaml
-# /etc/prometheus/rules/alert_rules.yml
-groups:
-  - name: availability
-    interval: 30s
-    rules:
-      - alert: ServiceDown
-        expr: up{job="my-app"} == 0
-        for: 1m
-        labels:
-          severity: critical
-        annotations:
-          summary: "Service {{ $labels.instance }} is down"
-          description: "{{ $labels.job }} has been down for more than 1 minute"
-
-      - alert: HighErrorRate
-        expr: job:http_requests_error_rate:percentage > 5
-        for: 5m
-        labels:
-          severity: warning
-        annotations:
-          summary: "High error rate for {{ $labels.job }}"
-          description: "Error rate is {{ $value }}% (threshold: 5%)"
-
-      - alert: HighLatency
-        expr: job:http_request_duration:p95 > 1
-        for: 5m
-        labels:
-          severity: warning
-        annotations:
-          summary: "High latency for {{ $labels.job }}"
-          description: "P95 latency is {{ $value }}s (threshold: 1s)"
-
-  - name: resources
-    interval: 1m
-    rules:
-      - alert: HighCPUUsage
-        expr: instance:node_cpu:utilization > 80
-        for: 5m
-        labels:
-          severity: warning
-        annotations:
-          summary: "High CPU usage on {{ $labels.instance }}"
-          description: "CPU usage is {{ $value }}%"
-
-      - alert: HighMemoryUsage
-        expr: instance:node_memory:utilization > 85
-        for: 5m
-        labels:
-          severity: warning
-        annotations:
-          summary: "High memory usage on {{ $labels.instance }}"
-          description: "Memory usage is {{ $value }}%"
-
-      - alert: DiskSpaceLow
-        expr: instance:node_disk:utilization > 90
-        for: 5m
-        labels:
-          severity: critical
-        annotations:
-          summary: "Low disk space on {{ $labels.instance }}"
-          description: "Disk usage is {{ $value }}%"
-```
-
-## Validation
-
-```bash
-# Validate configuration
-promtool check config prometheus.yml
-
-# Validate rules
-promtool check rules /etc/prometheus/rules/*.yml
-
-# Test query
-promtool query instant http://localhost:9090 'up'
-```
-
-**Reference:** See `scripts/validate-prometheus.sh`
-
-## Best Practices
-
-1. **Use consistent naming** for metrics (prefix_name_unit)
-2. **Set appropriate scrape intervals** (15-60s typical)
-3. **Use recording rules** for expensive queries
-4. **Implement high availability** (multiple Prometheus instances)
-5. **Configure retention** based on storage capacity
-6. **Use relabeling** for metric cleanup
-7. **Monitor Prometheus itself**
-8. **Implement federation** for large deployments
-9. **Use Thanos/Cortex** for long-term storage
-10. **Document custom metrics**
-
-## Troubleshooting
-
-**Check scrape targets:**
-```bash
-curl http://localhost:9090/api/v1/targets
-```
-
-**Check configuration:**
-```bash
-curl http://localhost:9090/api/v1/status/config
-```
-
-**Test query:**
-```bash
-curl 'http://localhost:9090/api/v1/query?query=up'
-```
-
-## Reference Files
-
-- `assets/prometheus.yml.template` - Complete configuration template
-- `references/scrape-configs.md` - Scrape configuration patterns
-- `references/recording-rules.md` - Recording rule examples
-- `scripts/validate-prometheus.sh` - Validation script
-
-## Related Skills
-
-- `grafana-dashboards` - For visualization
-- `slo-implementation` - For SLO monitoring
-- `distributed-tracing` - For request tracing

package/templates/skills/prompt-engineering-patterns/SKILL.md

@@ -1,201 +0,0 @@
----
-name: prompt-engineering-patterns
-description: Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability in production. Use when optimizing prompts, improving LLM outputs, or designing production prompt templates.
----
-
-# Prompt Engineering Patterns
-
-Master advanced prompt engineering techniques to maximize LLM performance, reliability, and controllability.
-
-## When to Use This Skill
-
-- Designing complex prompts for production LLM applications
-- Optimizing prompt performance and consistency
-- Implementing structured reasoning patterns (chain-of-thought, tree-of-thought)
-- Building few-shot learning systems with dynamic example selection
-- Creating reusable prompt templates with variable interpolation
-- Debugging and refining prompts that produce inconsistent outputs
-- Implementing system prompts for specialized AI assistants
-
-## Core Capabilities
-
-### 1. Few-Shot Learning
-- Example selection strategies (semantic similarity, diversity sampling)
-- Balancing example count with context window constraints
-- Constructing effective demonstrations with input-output pairs
-- Dynamic example retrieval from knowledge bases
-- Handling edge cases through strategic example selection
-
-### 2. Chain-of-Thought Prompting
-- Step-by-step reasoning elicitation
-- Zero-shot CoT with "Let's think step by step"
-- Few-shot CoT with reasoning traces
-- Self-consistency techniques (sampling multiple reasoning paths)
-- Verification and validation steps
-
-### 3. Prompt Optimization
-- Iterative refinement workflows
-- A/B testing prompt variations
-- Measuring prompt performance metrics (accuracy, consistency, latency)
-- Reducing token usage while maintaining quality
-- Handling edge cases and failure modes
-
-### 4. Template Systems
-- Variable interpolation and formatting
-- Conditional prompt sections
-- Multi-turn conversation templates
-- Role-based prompt composition
-- Modular prompt components
-
-### 5. System Prompt Design
-- Setting model behavior and constraints
-- Defining output formats and structure
-- Establishing role and expertise
-- Safety guidelines and content policies
-- Context setting and background information
-
-## Quick Start
-
-```python
-from prompt_optimizer import PromptTemplate, FewShotSelector
-
-# Define a structured prompt template
-template = PromptTemplate(
-    system="You are an expert SQL developer. Generate efficient, secure SQL queries.",
-    instruction="Convert the following natural language query to SQL:\n{query}",
-    few_shot_examples=True,
-    output_format="SQL code block with explanatory comments"
-)
-
-# Configure few-shot learning
-selector = FewShotSelector(
-    examples_db="sql_examples.jsonl",
-    selection_strategy="semantic_similarity",
-    max_examples=3
-)
-
-# Generate optimized prompt
-prompt = template.render(
-    query="Find all users who registered in the last 30 days",
-    examples=selector.select(query="user registration date filter")
-)
-```
-
-## Key Patterns
-
-### Progressive Disclosure
-Start with simple prompts, add complexity only when needed:
-
-1. **Level 1**: Direct instruction
-   - "Summarize this article"
-
-2. **Level 2**: Add constraints
-   - "Summarize this article in 3 bullet points, focusing on key findings"
-
-3. **Level 3**: Add reasoning
-   - "Read this article, identify the main findings, then summarize in 3 bullet points"
-
-4. **Level 4**: Add examples
-   - Include 2-3 example summaries with input-output pairs
-
-### Instruction Hierarchy
-```
-[System Context] → [Task Instruction] → [Examples] → [Input Data] → [Output Format]
-```
-
-### Error Recovery
-Build prompts that gracefully handle failures:
-- Include fallback instructions
-- Request confidence scores
-- Ask for alternative interpretations when uncertain
-- Specify how to indicate missing information
-
-## Best Practices
-
-1. **Be Specific**: Vague prompts produce inconsistent results
-2. **Show, Don't Tell**: Examples are more effective than descriptions
-3. **Test Extensively**: Evaluate on diverse, representative inputs
-4. **Iterate Rapidly**: Small changes can have large impacts
-5. **Monitor Performance**: Track metrics in production
-6. **Version Control**: Treat prompts as code with proper versioning
-7. **Document Intent**: Explain why prompts are structured as they are
-
-## Common Pitfalls
-
-- **Over-engineering**: Starting with complex prompts before trying simple ones
-- **Example pollution**: Using examples that don't match the target task
-- **Context overflow**: Exceeding token limits with excessive examples
-- **Ambiguous instructions**: Leaving room for multiple interpretations
-- **Ignoring edge cases**: Not testing on unusual or boundary inputs
-
-## Integration Patterns
-
-### With RAG Systems
-```python
-# Combine retrieved context with prompt engineering
-prompt = f"""Given the following context:
-{retrieved_context}
-
-{few_shot_examples}
-
-Question: {user_question}
-
-Provide a detailed answer based solely on the context above. If the context doesn't contain enough information, explicitly state what's missing."""
-```
-
-### With Validation
-```python
-# Add self-verification step
-prompt = f"""{main_task_prompt}
-
-After generating your response, verify it meets these criteria:
-1. Answers the question directly
-2. Uses only information from provided context
-3. Cites specific sources
-4. Acknowledges any uncertainty
-
-If verification fails, revise your response."""
-```
-
-## Performance Optimization
-
-### Token Efficiency
-- Remove redundant words and phrases
-- Use abbreviations consistently after first definition
-- Consolidate similar instructions
-- Move stable content to system prompts
-
-### Latency Reduction
-- Minimize prompt length without sacrificing quality
-- Use streaming for long-form outputs
-- Cache common prompt prefixes
-- Batch similar requests when possible
-
-## Resources
-
-- **references/few-shot-learning.md**: Deep dive on example selection and construction
-- **references/chain-of-thought.md**: Advanced reasoning elicitation techniques
-- **references/prompt-optimization.md**: Systematic refinement workflows
-- **references/prompt-templates.md**: Reusable template patterns
-- **references/system-prompts.md**: System-level prompt design
-- **assets/prompt-template-library.md**: Battle-tested prompt templates
-- **assets/few-shot-examples.json**: Curated example datasets
-- **scripts/optimize-prompt.py**: Automated prompt optimization tool
-
-## Success Metrics
-
-Track these KPIs for your prompts:
-- **Accuracy**: Correctness of outputs
-- **Consistency**: Reproducibility across similar inputs
-- **Latency**: Response time (P50, P95, P99)
-- **Token Usage**: Average tokens per request
-- **Success Rate**: Percentage of valid outputs
-- **User Satisfaction**: Ratings and feedback
-
-## Next Steps
-
-1. Review the prompt template library for common patterns
-2. Experiment with few-shot learning for your specific use case
-3. Implement prompt versioning and A/B testing
-4. Set up automated evaluation pipelines
-5. Document your prompt engineering decisions and learnings

package/templates/skills/prompt-engineering-patterns/assets/few-shot-examples.json

@@ -1,106 +0,0 @@
-{
-  "sentiment_analysis": [
-    {
-      "input": "This product exceeded my expectations! The quality is outstanding.",
-      "output": "Positive"
-    },
-    {
-      "input": "Terrible experience. The item arrived damaged and customer service was unhelpful.",
-      "output": "Negative"
-    },
-    {
-      "input": "The product works as described. Nothing special, but does the job.",
-      "output": "Neutral"
-    }
-  ],
-  "entity_extraction": [
-    {
-      "input": "Apple CEO Tim Cook announced the new iPhone at an event in Cupertino on September 12th.",
-      "output": {
-        "persons": ["Tim Cook"],
-        "organizations": ["Apple"],
-        "products": ["iPhone"],
-        "locations": ["Cupertino"],
-        "dates": ["September 12th"]
-      }
-    },
-    {
-      "input": "Microsoft acquired GitHub for $7.5 billion in 2018.",
-      "output": {
-        "persons": [],
-        "organizations": ["Microsoft", "GitHub"],
-        "products": [],
-        "locations": [],
-        "dates": ["2018"],
-        "monetary_values": ["$7.5 billion"]
-      }
-    }
-  ],
-  "code_generation": [
-    {
-      "input": "Write a Python function to check if a string is a palindrome",
-      "output": "def is_palindrome(s: str) -> bool:\n    \"\"\"Check if string is palindrome, ignoring case and spaces.\"\"\"\n    # Remove spaces and convert to lowercase\n    cleaned = s.replace(' ', '').lower()\n    # Compare with reversed string\n    return cleaned == cleaned[::-1]"
-    }
-  ],
-  "text_classification": [
-    {
-      "input": "How do I reset my password?",
-      "output": "account_management"
-    },
-    {
-      "input": "My order hasn't arrived yet. Where is it?",
-      "output": "shipping_inquiry"
-    },
-    {
-      "input": "I'd like to cancel my subscription.",
-      "output": "subscription_cancellation"
-    },
-    {
-      "input": "The app keeps crashing when I try to log in.",
-      "output": "technical_support"
-    }
-  ],
-  "data_transformation": [
-    {
-      "input": "John Smith, john@email.com, (555) 123-4567",
-      "output": {
-        "name": "John Smith",
-        "email": "john@email.com",
-        "phone": "(555) 123-4567"
-      }
-    },
-    {
-      "input": "Jane Doe | jane.doe@company.com | +1-555-987-6543",
-      "output": {
-        "name": "Jane Doe",
-        "email": "jane.doe@company.com",
-        "phone": "+1-555-987-6543"
-      }
-    }
-  ],
-  "question_answering": [
-    {
-      "context": "The Eiffel Tower is a wrought-iron lattice tower in Paris, France. It was constructed from 1887 to 1889 and stands 324 meters (1,063 ft) tall.",
-      "question": "When was the Eiffel Tower built?",
-      "answer": "The Eiffel Tower was constructed from 1887 to 1889."
-    },
-    {
-      "context": "Python 3.11 was released on October 24, 2022. It includes performance improvements and new features like exception groups and improved error messages.",
-      "question": "What are the new features in Python 3.11?",
-      "answer": "Python 3.11 includes exception groups, improved error messages, and performance improvements."
-    }
-  ],
-  "summarization": [
-    {
-      "input": "Climate change refers to long-term shifts in global temperatures and weather patterns. While climate change is natural, human activities have been the main driver since the 1800s, primarily due to the burning of fossil fuels like coal, oil and gas which produces heat-trapping greenhouse gases. The consequences include rising sea levels, more extreme weather events, and threats to biodiversity.",
-      "output": "Climate change involves long-term alterations in global temperatures and weather patterns, primarily driven by human fossil fuel consumption since the 1800s, resulting in rising sea levels, extreme weather, and biodiversity threats."
-    }
-  ],
-  "sql_generation": [
-    {
-      "schema": "users (id, name, email, created_at)\norders (id, user_id, total, order_date)",
-      "request": "Find all users who have placed orders totaling more than $1000",
-      "output": "SELECT u.id, u.name, u.email, SUM(o.total) as total_spent\nFROM users u\nJOIN orders o ON u.id = o.user_id\nGROUP BY u.id, u.name, u.email\nHAVING SUM(o.total) > 1000;"
-    }
-  ]
-}