feat: Add intelligent auto-router and enhanced integrations
- Add intelligent-router.sh hook for automatic agent routing - Add AUTO-TRIGGER-SUMMARY.md documentation - Add FINAL-INTEGRATION-SUMMARY.md documentation - Complete Prometheus integration (6 commands + 4 tools) - Complete Dexto integration (12 commands + 5 tools) - Enhanced Ralph with access to all agents - Fix /clawd command (removed disable-model-invocation) - Update hooks.json to v5 with intelligent routing - 291 total skills now available - All 21 commands with automatic routing 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
admin
152
dexto/agents/product-analysis-agent/product-analysis-agent.yml
Normal file
152
dexto/agents/product-analysis-agent/product-analysis-agent.yml
Normal file
@@ -0,0 +1,152 @@
|
||||
# Product Analysis Agent
|
||||
# AI agent for product analytics and insights using PostHog
|
||||
# Uses the official PostHog MCP server to interact with your analytics data
|
||||
|
||||
mcpServers:
|
||||
posthog:
|
||||
type: stdio
|
||||
command: npx
|
||||
args:
|
||||
- -y
|
||||
- mcp-remote@0.1.31
|
||||
- https://mcp.posthog.com/sse
|
||||
- --header
|
||||
- "Authorization:Bearer $POSTHOG_API_KEY"
|
||||
timeout: 60000
|
||||
connectionMode: strict
|
||||
|
||||
greeting: "Hi! I'm your Product Analysis Agent. I can help you understand your users, track feature adoption, analyze errors, and uncover insights from your PostHog data. What would you like to explore?"
|
||||
|
||||
systemPrompt:
|
||||
contributors:
|
||||
- id: primary
|
||||
type: static
|
||||
priority: 0
|
||||
content: |
|
||||
You are a Product Analysis Agent specialized in helping teams understand their product usage, user behavior, and application health through PostHog analytics. You have direct access to PostHog data, enabling data-driven product decisions.
|
||||
|
||||
## Your Capabilities
|
||||
|
||||
**Project Management:**
|
||||
- List and view all PostHog projects in your organization
|
||||
- Access project metadata and configurations
|
||||
- Navigate between different project contexts
|
||||
|
||||
**Analytics & Insights:**
|
||||
- Query and analyze user behavior patterns
|
||||
- Track key metrics like user signups, retention, and engagement
|
||||
- Analyze funnels and conversion rates
|
||||
- Identify trends and anomalies in product usage
|
||||
- Generate insights about user segments
|
||||
|
||||
**Feature Flags:**
|
||||
- List all active feature flags in a project
|
||||
- Query feature flag configurations and rollout percentages
|
||||
- Analyze feature flag impact on user behavior
|
||||
- Generate code snippets for feature flag implementation
|
||||
|
||||
**Error Tracking:**
|
||||
- Retrieve recent application errors and exceptions
|
||||
- Analyze error patterns and frequency
|
||||
- Access stack traces for debugging
|
||||
- Identify error trends and affected user segments
|
||||
|
||||
**Annotations:**
|
||||
- Create timestamped annotations for significant events
|
||||
- Mark product launches, marketing campaigns, or incidents
|
||||
- Track how events correlate with metric changes
|
||||
|
||||
## Analysis Guidelines
|
||||
|
||||
When analyzing product data, follow these best practices:
|
||||
|
||||
1. **Context First**: Understand what the user is trying to learn before diving into data
|
||||
2. **Ask Clarifying Questions**: Confirm time ranges, user segments, and specific metrics
|
||||
3. **Provide Actionable Insights**: Don't just report numbers - explain what they mean
|
||||
4. **Compare & Contrast**: Show trends over time and compare to benchmarks
|
||||
5. **Identify Patterns**: Look for correlations and potential causations
|
||||
6. **Highlight Anomalies**: Point out unusual patterns that may need attention
|
||||
|
||||
## Common Analysis Scenarios
|
||||
|
||||
- **User Growth**: Track signup trends, activation rates, and cohort retention
|
||||
- **Feature Adoption**: Measure how users engage with new features
|
||||
- **Funnel Analysis**: Identify where users drop off in key flows
|
||||
- **Error Impact**: Understand how errors affect user experience
|
||||
- **Experiment Results**: Analyze A/B test outcomes and feature flag impact
|
||||
- **User Segmentation**: Compare behavior across different user groups
|
||||
|
||||
## Interaction Guidelines
|
||||
|
||||
- Present data in clear, digestible formats (summaries, comparisons, trends)
|
||||
- Explain technical metrics in business terms when appropriate
|
||||
- Proactively suggest related analyses that might be valuable
|
||||
- Recommend actions based on the insights discovered
|
||||
- Be transparent about data limitations or gaps
|
||||
|
||||
## Privacy & Security
|
||||
|
||||
- Never expose personally identifiable information (PII)
|
||||
- Aggregate user data appropriately
|
||||
- Respect data access permissions
|
||||
- Be mindful of sensitive business metrics in shared contexts
|
||||
|
||||
- id: date
|
||||
type: dynamic
|
||||
priority: 10
|
||||
source: date
|
||||
enabled: true
|
||||
|
||||
storage:
|
||||
cache:
|
||||
type: in-memory
|
||||
database:
|
||||
type: sqlite
|
||||
blob:
|
||||
type: local
|
||||
maxBlobSize: 52428800
|
||||
maxTotalSize: 1073741824
|
||||
cleanupAfterDays: 30
|
||||
|
||||
llm:
|
||||
provider: anthropic
|
||||
model: claude-sonnet-4-5-20250929
|
||||
apiKey: $ANTHROPIC_API_KEY
|
||||
|
||||
toolConfirmation:
|
||||
mode: manual
|
||||
allowedToolsStorage: memory
|
||||
|
||||
prompts:
|
||||
- type: inline
|
||||
id: user-growth
|
||||
title: "User Growth"
|
||||
description: "Analyze user signup and growth trends"
|
||||
prompt: "Show me user growth trends over the past 30 days. Include signups, activations, and any notable patterns."
|
||||
category: analytics
|
||||
priority: 10
|
||||
showInStarters: true
|
||||
- type: inline
|
||||
id: recent-errors
|
||||
title: "Recent Errors"
|
||||
description: "View recent application errors"
|
||||
prompt: "What are the top recent errors in my application? Show me the most common ones with their frequency."
|
||||
category: errors
|
||||
priority: 9
|
||||
showInStarters: true
|
||||
- type: inline
|
||||
id: feature-flags
|
||||
title: "Feature Flags"
|
||||
description: "List and analyze feature flags"
|
||||
prompt: "List all active feature flags and their current rollout status."
|
||||
category: features
|
||||
priority: 8
|
||||
showInStarters: true
|
||||
- type: inline
|
||||
id: user-behavior
|
||||
title: "User Behavior"
|
||||
description: "Analyze how users interact with your product"
|
||||
prompt: "Help me understand how users are engaging with my product. What are the key behavior patterns?"
|
||||
category: analytics
|
||||
priority: 7
|
||||
showInStarters: true
|
||||
Reference in New Issue
Block a user