All categories
Research
Research, evidence gathering, literature, reports, investigation, and synthesis
- 30,315
- 1,264
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse research skills
Showing 11,017–11,040 of 30,315 skills
- Meta Research WorkflowApply systematic research methodology for multi-step research, fact-finding, web search, or verification tasks. Use when performing Brave Search, Puppeteer navigation, or synthesizing information from multiple sources.Votes: 0GitHub stars: 8
- Slack Daily SynthesisSynthesize Slack threads I participated in into the Logseq daily journal. Default mode walks backwards until finding a day already synthesized.Votes: 0GitHub stars: 8
- Process Needs Handy PlanFinds journal entries marked with [[Needs Handy Plan]], generates comprehensive construction/house project plans with tools, parts, safety, and instructions, creates Logseq pages, and removes labels after successVotes: 0GitHub stars: 8
- Process Book RecommendationsFinds journal entries marked with [[Book Recommendation]], researches books, integrates with book-sync system, creates wiki pages, and removes labels after successVotes: 0GitHub stars: 8
- Expand Missing TopicsExpand Missing Topics CommandVotes: 0GitHub stars: 8
- EnrichKnowledge Enrichment OrchestratorVotes: 0GitHub stars: 8
- Create ZettleTransforms any topic into a well-structured, interconnected Zettelkasten note optimized for Logseq with proper file pathsVotes: 0GitHub stars: 8
- MIGRATION NOTESKnowledge Processing Architecture Migration NotesVotes: 0GitHub stars: 8
- MIGRATION GUIDEMigration Guide: Unified [[Needs Processing]] TagVotes: 0GitHub stars: 8
- KNOWLEDGE PROCESSING ARCHITECTUREKnowledge Processing ArchitectureVotes: 0GitHub stars: 8
- Knowledge SynthesisSynthesize knowledge from multiple sources — including a conversation, PR, or investigation — into Zettelkasten notes for a personal Logseq wiki. Use when creating wiki pages, integrating academic research, building interconnected knowledge with [[links]] and #[[tags]], or whenever the user says "synthesize this to my wiki" / "add this to my wiki" / "synthesize this to my personal wiki" / "write this up in my notes."Votes: 0GitHub stars: 8
- Knowledge Literature ReviewConduct structured literature reviews by searching arXiv, building citation graphs via Semantic Scholar, and storing papers locally in the knowledge base. Use when asked to: review literature on a topic, map a research area, find key papers or state-of-the-art methods, explore citation networks, build a reading list, identify research gaps, expand from a seed paper to find related work, or understand what has been published in a field.Votes: 0GitHub stars: 8
- Journeys EnrichImproves existing docs/journeys/*.md spec files — fills in gaps flagged by journeys-extract, refines vague steps, and links plausible test_ids by searching the repo's test suite — without a full rediscovery pass and without clobbering fields owned by journeys-verify. Always proposes a before/after diff and waits for explicit approval before writing (plan-validate-execute), then applies via journeys-extract's upsert script so the verified→stale invariant stays enforced in one place. Use when a...Votes: 0GitHub stars: 8
- FullFull home project workflow — scope → research → plan → prep. Research and planning run in subagents. Hand off to /home:5-execute when ready to work.Votes: 0GitHub stars: 8
- Golang TroubleshootingTroubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber/cc-skills-golang@golang-benchmark` skill), applying opti...Votes: 0GitHub stars: 8
- Code Root Cause AnalysisSystematic investigation of errors, failures, and unexpected behaviors by searching personal-wiki history and external documentation. Use when debugging errors with stack traces, investigating incidents/outages, finding historical context for similar issues, analyzing recurring problems, or searching for past solutions. Combines Logseq knowledge base (journals, pages, incident notes) with web search for external docs. Follows structured methodology to extract error signatures, search historic...Votes: 0GitHub stars: 8
- Code ArchaeologySystematically analyze external codebases by cloning git repos or extracting archives to temp dirs, then reverse-engineering the code to extract functional/non-functional requirements, identify architectural patterns, document design choices, and catalog problems worth solving. Use when asked to analyze, understand, reverse-engineer, or evaluate an unfamiliar codebase.Votes: 0GitHub stars: 8
- Weekly Agency ReviewReview the week using accumulated session evidence — retrieval rates, hint depths, calibration accuracy, transfer and unassisted results. The learner identifies patterns and sets a strategy goal. Use weekly or after a multi-session period.Votes: 0GitHub stars: 4
- StrategizeFrames product design problems before solutions exist. Synthesizes research, sizes opportunities, defines hypotheses, scopes projects, and maps customer journeys. Use this skill for new project kickoffs, ambiguous business asks, translating research into briefs, strategic framing sessions, opportunity assessments, project scoping, stakeholder alignment, and competitive analysis—even if the user doesn't explicitly say "strategize."Votes: 0GitHub stars: 4
- PhilosopherA cross-cutting cognitive mode for sitting with design problems before rushing to solve them. Part of the Intent design strategy system. Activates expansive brainstorming: hyperassociativity, beginner's mind, cross-domain pattern recognition, and suppression of premature idea-dismissal. Works alongside every Intent skill — strategize uses it to reframe briefs, blueprint to question structural assumptions, journey to rethink interaction models, and specify to stress-test specs. Trigger when th...Votes: 0GitHub stars: 4
- MeasureDefines and tracks UX success through metrics, measurement frameworks, and experimentation. Part of the Intent design strategy system. Connects design decisions to observable evidence — did the thing we built actually help? Guards against measurement becoming manipulation. Trigger when: defining success metrics, designing A/B tests, building measurement frameworks, analyzing funnels, reviewing metric dashboards, questioning whether the right things are being measured, or when someone says "ho...Votes: 0GitHub stars: 4
- InvestigateGuide and conduct user research — from planning through synthesis. Interview scripts, survey design, usability test plans, diary studies, contextual inquiry. Plus synthesis: affinity mapping, thematic coding, insight extraction. Trigger when: planning user research, writing interview guides, designing usability tests, creating surveys, synthesizing research findings, "what should we research?", "how do I test this?", "write an interview guide", or any question about understanding users throug...Votes: 0GitHub stars: 4
- Write MdMarkdown readability, visual planning, and report HTML rendering. Load for any long research report (two passes: visual planning before figures, final readability after), when the user asks to improve readability or format a document, or when a report needs a self-contained HTML reading version. Handles language, structure, and a renderer-aware presentation layer. Horizontal slide decks belong to slide_deck.Votes: 0GitHub stars: 5
- Slide DeckSelf-contained HTML slide decks as a PPT replacement. Load when the user asks to present the project (or a subset such as motivation, contributions, methods, experiment results) as a horizontal-paging HTML file. Scrolling HTML report rendering belongs to write_md.Votes: 0GitHub stars: 5