daily-research
Daily AI research pipeline → Obsidian vault. Scans Reddit + X for agents, skills, models, MCP, RAG topics. Deduplicates against vault history, writes structured daily notes. Tag
Install with Tessl CLI
npx tessl i github:0xrabbidfly/eric-cartman --skill daily-research93
Quality
91%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at specificity and distinctiveness, clearly identifying a unique pipeline for AI research aggregation into Obsidian. However, it appears truncated (ending mid-word with 'Tag') and lacks an explicit 'Use when...' clause, which limits its completeness score. The technical domain terms are appropriate for the target audience.
Suggestions
Complete the truncated description and add an explicit 'Use when...' clause (e.g., 'Use when the user wants to aggregate daily AI news, research Reddit/X for AI topics, or update their Obsidian knowledge base with AI developments')
Ensure the full description is captured - currently ends with 'Tag' which appears cut off
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scans Reddit + X', 'Deduplicates against vault history', 'writes structured daily notes'. Clear domain (AI research) and specific platforms/outputs are named. | 3 / 3 |
Completeness | Clearly answers 'what' (scans sources, deduplicates, writes notes) but lacks explicit 'Use when...' clause. The description appears truncated (ends with 'Tag') and doesn't provide explicit trigger guidance. | 2 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'AI research', 'Reddit', 'X', 'Obsidian vault', 'agents', 'skills', 'models', 'MCP', 'RAG', 'daily notes'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche combining AI research topics, specific platforms (Reddit + X), and specific output format (Obsidian vault daily notes). Unlikely to conflict with other skills due to this unique combination. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill document that maximizes information density while remaining highly actionable. The pipeline flow is crystal clear, commands are executable, and the structure guides users from quick start through advanced configuration. The #keep/#kept feedback loop for long-term memory is particularly well-documented.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Obsidian is, how APIs work, or basic concepts. Every section delivers actionable information with minimal prose. The tables and structured lists maximize information density. | 3 / 3 |
Actionability | Provides copy-paste ready commands for all use cases (full run, single topic, dry-run, promote-only). Configuration is concrete with specific JSON keys and defaults. The pipeline flow is explicit with numbered steps. | 3 / 3 |
Workflow Clarity | Clear 6-step pipeline flow with explicit sequence. The promote/keep workflow has a clear feedback loop (add #keep → next run promotes → tag becomes #kept). The daily note structure diagram shows exactly what gets produced. | 3 / 3 |
Progressive Disclosure | Well-organized sections from Quick Start through Configuration. References to related skills (obsidian, last30days) are one level deep and clearly signaled. Config details are appropriately separated from core workflow. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.