social-intelligence
Search and monitor social media using X/Twitter (via Grok) and Reddit APIs. USE FOR: - Searching X/Twitter posts by keywords or hashtags - Finding X/Twitter users by criteria - Getting a user's recent posts - Searching Reddit posts and discussions - Getting comments from Reddit threads - Social media monitoring and research TRIGGERS: - "twitter", "X", "tweets", "posts on X" - "reddit", "subreddit", "reddit discussion" - "what are people saying", "social media", "sentiment" - "trending", "viral", "popular posts" - "user's posts", "timeline", "recent activity" Use `npx agentcash fetch` for Grok (X) and Reddit endpoints. All endpoints are $0.02 per call. IMPORTANT: Use exact endpoint paths from the Quick Reference table below.
Install with Tessl CLI
npx tessl i github:Merit-Systems/agentcash-skills --skill social-intelligence89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 is a well-crafted skill description that excels across all dimensions. It provides specific actions, comprehensive trigger terms that match natural user language, explicit 'USE FOR' and 'TRIGGERS' sections that clearly answer what and when, and platform-specific terminology that distinguishes it from other skills. The structured format with labeled sections enhances readability and Claude's ability to match user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Searching X/Twitter posts by keywords or hashtags', 'Finding X/Twitter users by criteria', 'Getting a user's recent posts', 'Searching Reddit posts and discussions', 'Getting comments from Reddit threads', 'Social media monitoring and research'. | 3 / 3 |
Completeness | Clearly answers both 'what' (search/monitor social media with specific actions listed under USE FOR) and 'when' (explicit TRIGGERS section with natural language patterns like 'what are people saying' and platform-specific terms). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say including 'twitter', 'X', 'tweets', 'reddit', 'subreddit', 'what are people saying', 'social media', 'sentiment', 'trending', 'viral', 'timeline' - these match how users naturally request social media tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on X/Twitter and Reddit APIs with distinct platform-specific triggers ('subreddit', 'tweets', 'posts on X'). Unlikely to conflict with general web search or other API skills due to explicit platform naming. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured API reference skill with excellent actionability through concrete, executable examples and good progressive disclosure. The main weaknesses are some verbosity in the response data section (which Claude could infer) and missing error handling/validation steps in the workflows, which is important for paid API calls that could fail.
Suggestions
Add error handling guidance to workflows: what to check if API returns errors, how to handle rate limits, and what to do if balance is insufficient
Trim or remove the 'Response Data' section - Claude can infer JSON field structures from context, or condense to a brief note about key fields only
Add a validation step after API calls in workflows to verify expected data was returned before proceeding to analysis steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code examples, but includes some redundancy (response data fields section is verbose and could be trimmed since Claude can infer JSON structure from examples). The workflows section repeats similar patterns that could be condensed. | 2 / 3 |
Actionability | Excellent actionability with fully executable bash commands, specific endpoint URLs, clear parameter documentation, and copy-paste ready examples for every operation. Each API call shows exact syntax with realistic payloads. | 3 / 3 |
Workflow Clarity | Workflows are presented as checklists with clear sequences, but lack explicit validation/error handling steps. No guidance on what to do if an API call fails, returns unexpected data, or if balance is insufficient despite the optional balance check. | 2 / 3 |
Progressive Disclosure | Well-structured with a quick reference table upfront, clear section organization, and appropriate external references (getting-started.md, rate-limits.md) that are one level deep and clearly signaled. Content is appropriately split between overview and detailed sections. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.