lucasilverentand/research-brief
plugins/project-docs/skills/research-brief/SKILL.md
Writes research brief documents from the project-docs template. Use when the user asks for a research brief, wants an evidence trail, needs sourced findings for a product or technical decision, or is filling research-brief.md.
$ install --global
skillsauthnpx skillsauth add lucasilverentand/skills research-briefInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 21, 2026, 7:18 AM205.1s2 files scanned
SKILL.md
- name:
- research-brief
- description:
- Writes research brief documents from the project-docs template. Use when the user asks for a research brief, wants an evidence trail, needs sourced findings for a product or technical decision, or is filling research-brief.md.
Research Brief
Use this skill to preserve evidence, source quality, implications, and follow-up questions without turning product or technical docs into source dumps.
Decision tree
- What is the user asking for?
- A new research brief -> read
../../README.mdandreferences/template.md, then draft the brief around one focused research question. - Evidence for a decision already made -> use the
decision-recordskill for the decision and link to this research brief for source detail. - Vendor, API, OS, framework, or hardware analysis -> use
platform-dependencywhen the dependency itself is the durable subject; use this skill for focused supporting research. - Live or recent facts -> verify with current primary sources before writing findings.
- Something else -> ask for the research question the brief should answer.
- A new research brief -> read
Workflow
- Read
../../README.mdfor shared conventions and relationship rules. - Read
references/template.mdbefore drafting or editing. - Frame one research question. Split broad investigations into multiple briefs.
- Capture sources, findings, evidence quality, implications, risks, recommendation, and follow-up questions.
- Keep source summaries short. Link to source material and explain why it matters.
- Make uncertainty visible. Distinguish confirmed findings, weak signals, and guesses.
Document contract
- When to write: When evidence needs its own source trail before a product, dependency, or implementation decision.
- How many: One per focused research question.
- Owns: Research question, source trail, findings, evidence quality, implications, risks, recommendation, and follow-up questions.
- Link instead of duplicating: Decisions belong in decision records; implementation plans belong in technical designs; dependency contracts belong in platform dependency docs.
Related Skills
lucasilverentand/open-source-docs
tools
VerifiedTrustedCommunity
Creates, audits, and updates public open-source repository documentation, including README files, CONTRIBUTING guides, SECURITY and SUPPORT docs, project badges, quickstarts, usage guidance, community links, and contributor onboarding. Use when maintaining docs for public GitHub projects, libraries, CLIs, apps, or reusable packages, especially when the user says "update this README", "write CONTRIBUTING.md", "make these docs open-source ready", or "improve the public project docs".
3SKILL.mdUpdated Jun 5, 2026
lucasilverentand/closed-source-docs
development
VerifiedTrustedCommunity
Creates, audits, and updates private or closed-source project documentation, including internal README hubs, codebase navigation guides, ownership links, Linear initiative links, onboarding notes, runbooks, and contribution guidance for teams. Use when maintaining docs for private repositories, internal apps, services, infrastructure, or company projects, especially when the user says "make this README an internal hub", "document how to navigate this repo", "add Linear links to the docs", or "write private project documentation".
3SKILL.mdUpdated Jun 5, 2026
lucasilverentand/linear-issues
development
VerifiedTrustedCommunity
Creates, updates, estimates, and tidies Linear issues using Luca's issue-shaping rules. Use when the user asks to create a Linear issue, write ticket-ready issue text, refine an existing issue, add acceptance criteria, set issue relationships, estimate points, audit issue hygiene, tidy a Linear project, find duplicates, fix stale blockers, or normalize labels, milestones, priorities, and issue state.
3SKILL.mdUpdated Jun 5, 2026
lucasilverentand/tidy-linear-project
testing
VerifiedTrustedCommunity
Keeps an existing Linear project tidy after planning and during execution. Use when the user asks to "tidy Linear", "clean up the project", "audit issues", "find duplicates", "check stale blockers", "fix project drift", or run periodic Linear housekeeping on a project, initiative, or milestone set. Use when planning is underway or execution has started and relationships, labels, priorities, documents, and issue states need coherence without changing product scope.
3SKILL.mdUpdated May 29, 2026