ClawTrust
7.9
/ 10
1 evaluations
3.4k Downloads
Overview
Automate generation of structured daily, weekly, and alert reports for a lead/outreach pipeline, while persisting key metrics and notes into dated markdown memory files for ongoing progress tracking.
Key Advantages
1.Clear, opinionated report templates for morning, end-of-day, and weekly summaries focused on lead generation and outreach workflows.
2.Built-in structure for tracking pipeline stages, budgets, and performance vs targets, reducing ad-hoc reporting overhead.
3.Persistent markdown-based memory (YYYY-MM-DD.md) that standardizes how metrics, issues, and next-day tasks are logged.
4.Local model (Ollama) usage for simple aggregation, minimizing cost and dependency on remote APIs.
5.Alerting logic for critical events (replies, budget thresholds, API errors, blocked tasks) to reduce the chance of missing important signals.
Use Cases
- Daily monitoring of lead sourcing, outreach, and cost metrics for a solo founder or small sales team.
- Creating consistent morning and EOD briefings for a growth marketing or outbound team working in a specific timezone (e.g., Spain).
- Weekly performance reviews summarizing leads, outreach, replies, qualification, closes, and conversions versus revenue targets.
- Maintaining a chronological memory log of issues, notes, and next-day tasks to give AI agents or humans rich context over time.
- Triggering immediate alerts to Telegram (or similar messaging) when replies are detected, budgets approach depletion, or workflows are blocked.
Evaluation Scores
7.9
/ 10
Reliability
7.8
Functionality
7.2
Usability
7.9
Safety
8.8
Performance
8.3
Compatibility
7.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.9/103/19/2026▼
OS: win32-x64LLM: google/gemini-3-flash-preview
This skill is a focused reporting and memory layer for lead-generation and outreach operations, best suited for users who already have data sources or agents producing metrics and want them turned into consistent briefings and logs. It excels at enforcing a clear cadence (morning, EOD, weekly) and a disciplined markdown memory format, and it leverages a local model so cost and latency are low.
Main risks and limitations: it appears specialized to a particular workflow (lead/outreach with budget tracking), so it may require customization to fit very different pipelines; it relies on correct upstream metric integration and scheduling to be truly reliable; and stored logs may contain sensitive business and contact data, so users must ensure secure storage and access control. Recommended scenarios include solo founders, small SDR/growth teams, and AI-agent setups that need lightweight but structured reporting, alerting on key events, and long-term context persistence without relying on expensive remote models.
Comments (0)
No comments yet. Be the first!