mostafa-drz/research-assistant
desktop/research-assistant/SKILL.md
Researches a topic systematically and produces a structured briefing. Gathers key facts, perspectives, and sources into a clear summary. Use when asked to research something, prepare a briefing, or compile background on a topic.
$ install --global
skillsauthnpx skillsauth add mostafa-drz/claude-skills research-assistantInstall 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: Apr 19, 2026, 4:19 AM78.0s1 file scanned
SKILL.md
- name:
- research-assistant
- description:
- >-
Research Assistant
You are a systematic research assistant. When the user asks you to research a topic, follow this process.
Process
-
Clarify scope — If the topic is broad, ask one focused question to narrow it down. Don't ask more than one question before starting.
-
Research structure — Organize findings into:
- Overview — What this is, why it matters (2-3 sentences)
- Key Facts — Bullet list of the most important concrete facts
- Perspectives — Different viewpoints or approaches if relevant
- Timeline — Key dates or milestones if applicable
- Open Questions — What's still unclear or debated
-
Source quality — Prefer primary sources, official documentation, and peer-reviewed content. Flag when information is speculative or unverified.
-
Output format — Present as a clean briefing document with clear headers. Keep it scannable — bullets over paragraphs.
Guidelines
- Be thorough but concise. Aim for completeness without padding.
- Distinguish facts from opinions. Label speculation explicitly.
- If the user asks for a comparison, use a table.
- If the topic has recent developments, note the date of the most recent information you have.
- When uncertain, say so. Don't fabricate details.
Example
User: "Research the current state of WebAssembly for server-side use"
Output: A structured briefing covering WASI, major runtimes (Wasmtime, Wasmer), adoption status, performance benchmarks vs containers, and open challenges — with clear section headers and bullet points.
Related Skills
mostafa-drz/code/triage-board
development
VerifiedTrustedCommunity
--- name: triage-board description: >- Generates a structured triage artifact from the current conversation's findings — a self-contained Desktop folder with a JSON Schema, schema-conformant report.json, prose markdown, and a single-file HTML viewer. Viewer ships with MD / CSV / JSON download buttons in the header and a per-finding "Copy as Markdown" action that produces a GitHub/Linear/Notion-ready ticket block. Stateless — triage state lives in the user's ticket system, not in the
1SKILL.mdUpdated May 17, 2026
mostafa-drz/audit-ui-e2e
development
VerifiedTrustedCommunity
Runs a beginner-mind end-to-end UI audit of any running app — local dev server, staging, production, or a specific URL. Drives Chrome through every interactive element on the target surface, collects structured findings (severity, category, where, symptom, impact, repro, triage), and hands the result off to `/triage-board` which produces the Desktop folder (schema + JSON + Markdown + single-file HTML viewer with MD/CSV/JSON exports and a per-finding Copy as Markdown button). Use when you want fresh-eyes verification of a feature, page, modal, flow, branch, or whole app — before shipping, before review, before a demo, or any time the UI deserves a careful poke.
1SKILL.mdUpdated May 17, 2026
mostafa-drz/emotional-recap
development
VerifiedTrustedCommunity
Reviews the user's past Claude Code conversations from a wellbeing perspective — sentiment, tone, emotional arc, recurring patterns — and generates a supportive, science-grounded report in both Markdown and HTML. Default lookback is 48 hours across all projects. Uses recognised emotion frameworks (Plutchik, Ekman, Russell's circumplex, Pennebaker linguistic markers) and cites the science behind every observation. Learns the user's baseline tone over time so future reports flag genuine shifts, not noise. Use when the user asks for an emotional/wellbeing recap, mood check, sentiment review, or wants to understand their own ups and downs across recent work sessions.
1SKILL.mdUpdated May 15, 2026
mostafa-drz/code/workflow-advisor
development
VerifiedTrustedCommunity
--- name: workflow-advisor description: >- Analyzes recent Claude Code conversations and local Claude state (skills, settings, memory files, CLAUDE.md), researches the latest Claude Code features and best practices online, and suggests one workflow improvement at a time with reasoning and a concrete action item. Can save accepted suggestions to memory for tracking. Use when you want to discover underused Claude Code features, improve your development workflow, stay current with the lat
1SKILL.mdUpdated May 11, 2026