research-software
Made by JeffResearch software tools via source code, GitHub, web. Use when creating skills, learning new tools, finding undocumented features, or bleeding-edge patterns.
Works With
Quality and Utility come from canonical skill metadata. Community ratings appear separately as stars when subscriber reviews exist.
Subscribe to download
Public previews are available, but downloads, CLI sync, and premium content require an active subscription.
Sign In to Subscribe- Full skill content with deterministic versioning
- CLI sync + local search index
- Access to Jeffrey’s premium library
Save to your account
Saved skills live in your cloud list. Run jsm sync on each machine to pull them locally.
What's New with this Skill
1Updates, enhancements, and release notes for this skill.
New: Research Software, clone the latest stable tag, read the source, skip Stack Overflow
Documentation lags behind code, and old forum answers describe APIs that have since changed. The skill is the discipline: clone to /tmp, check out the latest stable tag (not main), spawn an Explore agent on the source, filter web results to 2025–2026, and produce a structured research report instead of a blob of notes. Four rules: latest stable tag, 2025–2026 sources only, code over docs, skip Stack Overflow.
- Output-first: every research session produces the same structured report (tool, version, commands, config, env vars, gotchas with citations, sources)
- Rules: latest stable tag (never main), code over docs, 2025–2026 sources only, skip Stack Overflow. The agent doesn't accept "the docs say X" without finding X in the code
- Spawn an Explore agent on the cloned source for the deep dive; parallel GitHub PR/issue pulls and web searches filtered to 2025–2026 catch the recent additions
- Citations are mandatory: every gotcha names the PR, issue, or code location that proves the claim, and the sources section lists repo@commit, PR numbers, and post URLs
- Source priority: source code, then recent PRs, GitHub issues, 2025–2026 blog posts, and official docs last (often outdated). Stack Overflow and anything pre-2025 are skipped
- Output templates per research type (CLI tool, library/framework, tool comparison, minimal quick research) live in references/OUTPUT-TEMPLATES.md
The output shape is the contract. Every research session produces the same document: tool name and version, repo and commit pinned, commands table (task / command / notes), config table, env vars table, gotchas with citations to PR/issue/code, and a sources section linking back to the file:line, PR numbers, and dated posts that informed each claim.