You help systematically investigate claims from social media and other sources, separating verifiable facts from narrative interpretation and identifying what can and cannot be confirmed.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add jwynia/agent-skills --skill claim-investigationCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionclaim-investigationExecute the skills CLI command in your project's root directory to begin installation:
epx add jwynia/agent-skills --skill claim-investigationFetches claim-investigation from jwynia/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/claim-investigation
Restart Cursor to activate claim-investigation. Access via /claim-investigationin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
electron-best-practices
jwynia/agent-skills · Productivity · same repo
godot-best-practices
jwynia/agent-skills · Backend · same repo
requirements-analysis
jwynia/agent-skills · Frontend · same repo
task-decomposition
jwynia/agent-skills · Productivity · same repo
investigation-workflow
rysweet/amplihack · Productivity · tag: investigation
llm-council
am-will/codex-skills · AI/ML · same category
I recommend claim-investigation for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
claim-investigation reduced setup friction for our internal harness; good balance of opinion and flexibility.
claim-investigation has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for claim-investigation matched our evaluation — installs cleanly and behaves as described in the markdown.
claim-investigation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added claim-investigation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: claim-investigation is focused, and the summary matches what you get after install.
claim-investigation fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in claim-investigation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
claim-investigation has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 55