@ngxtm/devkit 3.0.3 → 3.2.0

package/skills/evaluation/SKILL.md

@@ -0,0 +1,238 @@
+---
+name: evaluation
+description: "Build evaluation frameworks for agent systems"
+source: "https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering/tree/main/skills/evaluation"
+risk: safe
+---
+
+## When to Use This Skill
+
+Build evaluation frameworks for agent systems
+
+Use this skill when working with build evaluation frameworks for agent systems.
+# Evaluation Methods for Agent Systems
+
+Evaluation of agent systems requires different approaches than traditional software or even standard language model applications. Agents make dynamic decisions, are non-deterministic between runs, and often lack single correct answers. Effective evaluation must account for these characteristics while providing actionable feedback. A robust evaluation framework enables continuous improvement, catches regressions, and validates that context engineering choices achieve intended effects.
+
+## When to Activate
+
+Activate this skill when:
+- Testing agent performance systematically
+- Validating context engineering choices
+- Measuring improvements over time
+- Catching regressions before deployment
+- Building quality gates for agent pipelines
+- Comparing different agent configurations
+- Evaluating production systems continuously
+
+## Core Concepts
+
+Agent evaluation requires outcome-focused approaches that account for non-determinism and multiple valid paths. Multi-dimensional rubrics capture various quality aspects: factual accuracy, completeness, citation accuracy, source quality, and tool efficiency. LLM-as-judge provides scalable evaluation while human evaluation catches edge cases.
+
+The key insight is that agents may find alternative paths to goals—the evaluation should judge whether they achieve right outcomes while following reasonable processes.
+
+**Performance Drivers: The 95% Finding**
+Research on the BrowseComp evaluation (which tests browsing agents' ability to locate hard-to-find information) found that three factors explain 95% of performance variance:
+
+| Factor | Variance Explained | Implication |
+|--------|-------------------|-------------|
+| Token usage | 80% | More tokens = better performance |
+| Number of tool calls | ~10% | More exploration helps |
+| Model choice | ~5% | Better models multiply efficiency |
+
+This finding has significant implications for evaluation design:
+- **Token budgets matter**: Evaluate agents with realistic token budgets, not unlimited resources
+- **Model upgrades beat token increases**: Upgrading to Claude Sonnet 4.5 or GPT-5.2 provides larger gains than doubling token budgets on previous versions
+- **Multi-agent validation**: The finding validates architectures that distribute work across agents with separate context windows
+
+## Detailed Topics
+
+### Evaluation Challenges
+
+**Non-Determinism and Multiple Valid Paths**
+Agents may take completely different valid paths to reach goals. One agent might search three sources while another searches ten. They might use different tools to find the same answer. Traditional evaluations that check for specific steps fail in this context.
+
+The solution is outcome-focused evaluation that judges whether agents achieve right outcomes while following reasonable processes.
+
+**Context-Dependent Failures**
+Agent failures often depend on context in subtle ways. An agent might succeed on simple queries but fail on complex ones. It might work well with one tool set but fail with another. Failures may emerge only after extended interaction when context accumulates.
+
+Evaluation must cover a range of complexity levels and test extended interactions, not just isolated queries.
+
+**Composite Quality Dimensions**
+Agent quality is not a single dimension. It includes factual accuracy, completeness, coherence, tool efficiency, and process quality. An agent might score high on accuracy but low in efficiency, or vice versa.
+
+Evaluation rubrics must capture multiple dimensions with appropriate weighting for the use case.
+
+### Evaluation Rubric Design
+
+**Multi-Dimensional Rubric**
+Effective rubrics cover key dimensions with descriptive levels:
+
+Factual accuracy: Claims match ground truth (excellent to failed)
+
+Completeness: Output covers requested aspects (excellent to failed)
+
+Citation accuracy: Citations match claimed sources (excellent to failed)
+
+Source quality: Uses appropriate primary sources (excellent to failed)
+
+Tool efficiency: Uses right tools reasonable number of times (excellent to failed)
+
+**Rubric Scoring**
+Convert dimension assessments to numeric scores (0.0 to 1.0) with appropriate weighting. Calculate weighted overall scores. Determine passing threshold based on use case requirements.
+
+### Evaluation Methodologies
+
+**LLM-as-Judge**
+LLM-based evaluation scales to large test sets and provides consistent judgments. The key is designing effective evaluation prompts that capture the dimensions of interest.
+
+Provide clear task description, agent output, ground truth (if available), evaluation scale with level descriptions, and request structured judgment.
+
+**Human Evaluation**
+Human evaluation catches what automation misses. Humans notice hallucinated answers on unusual queries, system failures, and subtle biases that automated evaluation misses.
+
+Effective human evaluation covers edge cases, samples systematically, tracks patterns, and provides contextual understanding.
+
+**End-State Evaluation**
+For agents that mutate persistent state, end-state evaluation focuses on whether the final state matches expectations rather than how the agent got there.
+
+### Test Set Design
+
+**Sample Selection**
+Start with small samples during development. Early in agent development, changes have dramatic impacts because there is abundant low-hanging fruit. Small test sets reveal large effects.
+
+Sample from real usage patterns. Add known edge cases. Ensure coverage across complexity levels.
+
+**Complexity Stratification**
+Test sets should span complexity levels: simple (single tool call), medium (multiple tool calls), complex (many tool calls, significant ambiguity), and very complex (extended interaction, deep reasoning).
+
+### Context Engineering Evaluation
+
+**Testing Context Strategies**
+Context engineering choices should be validated through systematic evaluation. Run agents with different context strategies on the same test set. Compare quality scores, token usage, and efficiency metrics.
+
+**Degradation Testing**
+Test how context degradation affects performance by running agents at different context sizes. Identify performance cliffs where context becomes problematic. Establish safe operating limits.
+
+### Continuous Evaluation
+
+**Evaluation Pipeline**
+Build evaluation pipelines that run automatically on agent changes. Track results over time. Compare versions to identify improvements or regressions.
+
+**Monitoring Production**
+Track evaluation metrics in production by sampling interactions and evaluating randomly. Set alerts for quality drops. Maintain dashboards for trend analysis.
+
+## Practical Guidance
+
+### Building Evaluation Frameworks
+
+1. Define quality dimensions relevant to your use case
+2. Create rubrics with clear, actionable level descriptions
+3. Build test sets from real usage patterns and edge cases
+4. Implement automated evaluation pipelines
+5. Establish baseline metrics before making changes
+6. Run evaluations on all significant changes
+7. Track metrics over time for trend analysis
+8. Supplement automated evaluation with human review
+
+### Avoiding Evaluation Pitfalls
+
+Overfitting to specific paths: Evaluate outcomes, not specific steps.
+Ignoring edge cases: Include diverse test scenarios.
+Single-metric obsession: Use multi-dimensional rubrics.
+Neglecting context effects: Test with realistic context sizes.
+Skipping human evaluation: Automated evaluation misses subtle issues.
+
+## Examples
+
+**Example 1: Simple Evaluation**
+```python
+def evaluate_agent_response(response, expected):
+    rubric = load_rubric()
+    scores = {}
+    for dimension, config in rubric.items():
+        scores[dimension] = assess_dimension(response, expected, dimension)
+    overall = weighted_average(scores, config["weights"])
+    return {"passed": overall >= 0.7, "scores": scores}
+```
+
+**Example 2: Test Set Structure**
+
+Test sets should span multiple complexity levels to ensure comprehensive evaluation:
+
+```python
+test_set = [
+    {
+        "name": "simple_lookup",
+        "input": "What is the capital of France?",
+        "expected": {"type": "fact", "answer": "Paris"},
+        "complexity": "simple",
+        "description": "Single tool call, factual lookup"
+    },
+    {
+        "name": "medium_query",
+        "input": "Compare the revenue of Apple and Microsoft last quarter",
+        "complexity": "medium",
+        "description": "Multiple tool calls, comparison logic"
+    },
+    {
+        "name": "multi_step_reasoning",
+        "input": "Analyze sales data from Q1-Q4 and create a summary report with trends",
+        "complexity": "complex",
+        "description": "Many tool calls, aggregation, analysis"
+    },
+    {
+        "name": "research_synthesis",
+        "input": "Research emerging AI technologies, evaluate their potential impact, and recommend adoption strategy",
+        "complexity": "very_complex",
+        "description": "Extended interaction, deep reasoning, synthesis"
+    }
+]
+```
+
+## Guidelines
+
+1. Use multi-dimensional rubrics, not single metrics
+2. Evaluate outcomes, not specific execution paths
+3. Cover complexity levels from simple to complex
+4. Test with realistic context sizes and histories
+5. Run evaluations continuously, not just before release
+6. Supplement LLM evaluation with human review
+7. Track metrics over time for trend detection
+8. Set clear pass/fail thresholds based on use case
+
+## Integration
+
+This skill connects to all other skills as a cross-cutting concern:
+
+- context-fundamentals - Evaluating context usage
+- context-degradation - Detecting degradation
+- context-optimization - Measuring optimization effectiveness
+- multi-agent-patterns - Evaluating coordination
+- tool-design - Evaluating tool effectiveness
+- memory-systems - Evaluating memory quality
+
+## References
+
+Internal reference:
+- [Metrics Reference](./references/metrics.md) - Detailed evaluation metrics and implementation
+
+## References
+
+Internal skills:
+- All other skills connect to evaluation for quality measurement
+
+External resources:
+- LLM evaluation benchmarks
+- Agent evaluation research papers
+- Production monitoring practices
+
+---
+
+## Skill Metadata
+
+**Created**: 2025-12-20
+**Last Updated**: 2025-12-20
+**Author**: Agent Skills for Context Engineering Contributors
+**Version**: 1.0.0

package/skills/event-sourcing-architect/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: event-sourcing-architect
+description: "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trails, or temporal queries."
+---
+
+# Event Sourcing Architect
+
+Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.
+
+## Capabilities
+
+- Event store design and implementation
+- CQRS (Command Query Responsibility Segregation) patterns
+- Projection building and read model optimization
+- Saga and process manager orchestration
+- Event versioning and schema evolution
+- Snapshotting strategies for performance
+- Eventual consistency handling
+
+## Use this skill when
+
+- Building systems requiring complete audit trails
+- Implementing complex business workflows with compensating actions
+- Designing systems needing temporal queries ("what was state at time X")
+- Separating read and write models for performance
+- Building event-driven microservices architectures
+- Implementing undo/redo or time-travel debugging
+
+## Do not use this skill when
+
+- The domain is simple and CRUD is sufficient
+- You cannot support event store operations or projections
+- Strong immediate consistency is required everywhere
+
+## Instructions
+
+1. Identify aggregate boundaries and event streams
+2. Design events as immutable facts
+3. Implement command handlers and event application
+4. Build projections for query requirements
+5. Design saga/process managers for cross-aggregate workflows
+6. Implement snapshotting for long-lived aggregates
+7. Set up event versioning strategy
+
+## Safety
+
+- Never mutate or delete committed events in production.
+- Rebuild projections in staging before running in production.
+
+## Best Practices
+
+- Events are facts - never delete or modify them
+- Keep events small and focused
+- Version events from day one
+- Design for eventual consistency
+- Use correlation IDs for tracing
+- Implement idempotent event handlers
+- Plan for projection rebuilding