Logseq Review Workflow Eval
logseq/logseq
Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…
Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-research-phase --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/gsd-research-phase .claude/skills/gsd-research-phase && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "gsd-research-phase" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-research-phase into .claude/skills/gsd-research-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-research-phase", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-research-phaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-research-phase --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/gsd-research-phase .agents/skills/gsd-research-phase && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gsd-research-phase" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-research-phase into .agents/skills/gsd-research-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-research-phase", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-research-phase --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/gsd-research-phase .cursor/skills/gsd-research-phase && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "gsd-research-phase" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-research-phase into .cursor/skills/gsd-research-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-research-phase", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/SpillwaveSolutions/agent-brain.git --path .codex/skills/gsd-research-phase--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-research-phase --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/gsd-research-phase .gemini/skills/gsd-research-phase && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "gsd-research-phase" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-research-phase into .gemini/skills/gsd-research-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-research-phase", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install SpillwaveSolutions/agent-brain gsd-research-phaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/gsd-research-phase .github/skills/gsd-research-phase && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "gsd-research-phase" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-research-phase into .github/skills/gsd-research-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-research-phase", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SpillwaveSolutions/agent-brain gsd-research-phase --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SpillwaveSolutions/agent-brain.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/gsd-research-phase .opencode/skills/gsd-research-phase && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "gsd-research-phase" agent skill from https://github.com/SpillwaveSolutions/agent-brain/tree/main/.codex/skills/gsd-research-phase into .opencode/skills/gsd-research-phase/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsd-research-phase", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
gsd-research-phaseResearch how to implement a phase (standalone - usually use $gsd-plan-phase instead)
Gsd Research Phase is an agent skill from SpillwaveSolutions/agent-brain. Research how to implement a phase (standalone - usually use $gsd-plan-phase instead)
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management. The repository describes itself as: Local-first RAG memory for AI agents: hybrid + GraphRAG search, MCP server with OAuth 2.1, plugin for Claude Code / OpenCode / Codex. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 8339623. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
nodeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Gsd Research Phase loads about 1.9k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 505 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from SpillwaveSolutions/agent-brain at commit 8339623, republished under its MIT licence (© SpillwaveSolutions). 505 words, ~1,917 tokens.
.claude/skills/gsd-research-phase/SKILL.md (or your agent's skills folder).<codex_skill_adapter>
$gsd-research-phase.$gsd-research-phase as {{GSD_ARGS}}.{{GSD_ARGS}} as empty.GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header → headerquestion → question"Label" — description → {label: "Label", description: "description"}id from header: lowercase, replace spaces with underscoresBatched calls:
AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]Multi-select workaround:
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.Execute mode fallback:
request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y") → spawn_agent(agent_type="X", message="Y")Task(model="...") → omit (Codex uses per-role config, not inline model selection)fork_context: false by default — GSD agents load their own context via <files_to_read> blocksParallel fan-out:
wait(ids) for all to completeResult parsing:
CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.close_agent(id) after collecting results from each agent
</codex_skill_adapter><objective>
Research how to implement a phase. Spawns gsd-phase-researcher agent with phase context.
Note: This is a standalone research command. For most workflows, use $gsd-plan-phase which integrates research automatically.
Use this command when:
Orchestrator role: Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.
Why subagent: Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
</objective>
<available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
<context>
Phase number: {{GSD_ARGS}} (required)
Normalize phase input in step 1 before any directory lookups.
</context>
<process>
INIT=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" init phase-op "{{GSD_ARGS}}")
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fiExtract from init JSON: phase_dir, phase_number, phase_name, phase_found, commit_docs, has_research, state_path, requirements_path, context_path, research_path.
Resolve researcher model:
RESEARCHER_MODEL=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" resolve-model gsd-phase-researcher --raw)PHASE_INFO=$(node "/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/bin/gsd-tools.cjs" roadmap get-phase "${phase_number}")If found is false: Error and exit. If found is true: Extract phase_number, phase_name, goal from JSON.
ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/nullIf exists: Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.
If doesn't exist: Continue.
Use paths from INIT (do not inline file contents in orchestrator context):
requirements_pathcontext_pathstate_pathPresent summary with phase description and what files the researcher will load.
Research modes: ecosystem (default), feasibility, implementation, comparison.
<research_type>
Phase Research — investigating HOW to implement a specific phase well.
</research_type>
<key_insight>
The question is NOT "which library should I use?"
The question is: "What do I not know that I don't know?"
For this phase, discover:
- What's the established architecture pattern?
- What libraries form the standard stack?
- What problems do people commonly hit?
- What's SOTA vs what the agent's training thinks is SOTA?
- What should NOT be hand-rolled?
</key_insight>
<objective>
Research implementation approach for Phase {phase_number}: {phase_name}
Mode: ecosystem
</objective>
<files_to_read>
- {requirements_path} (Requirements)
- {context_path} (Phase context from discuss-phase, if exists)
- {state_path} (Prior project decisions and blockers)
</files_to_read>
<additional_context>
**Phase description:** {phase_description}
</additional_context>
<downstream_consumer>
Your RESEARCH.md will be loaded by `$gsd-plan-phase` which uses specific sections:
- `## Standard Stack` → Plans use these libraries
- `## Architecture Patterns` → Task structure follows these
- `## Don't Hand-Roll` → Tasks NEVER build custom solutions for listed problems
- `## Common Pitfalls` → Verification steps check for these
- `## Code Examples` → Task actions reference these patterns
Be prescriptive, not exploratory. "Use X" not "Consider X or Y."
</downstream_consumer>
<quality_gate>
Before declaring complete, verify:
- [ ] All domains investigated (not just some)
- [ ] Negative claims verified with official docs
- [ ] Multiple sources for critical claims
- [ ] Confidence levels assigned honestly
- [ ] Section names match what plan-phase expects
</quality_gate>
<output>
Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
</output>Task(
prompt=filled_prompt,
subagent_type="gsd-phase-researcher",
model="{researcher_model}",
description="Research Phase {phase}"
)## RESEARCH COMPLETE: Display summary, offer: Plan phase, Dig deeper, Review full, Done.
## CHECKPOINT REACHED: Present to user, get response, spawn continuation.
## RESEARCH INCONCLUSIVE: Show what was attempted, offer: Add context, Try different mode, Manual.
<objective>
Continue research for Phase {phase_number}: {phase_name}
</objective>
<prior_state>
<files_to_read>
- .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md (Existing research)
</files_to_read>
</prior_state>
<checkpoint_response>
**Type:** {checkpoint_type}
**Response:** {user_response}
</checkpoint_response>Task(
prompt=continuation_prompt,
subagent_type="gsd-phase-researcher",
model="{researcher_model}",
description="Continue research Phase {phase}"
)</process>
<success_criteria>
© SpillwaveSolutions, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .codex/skills/gsd-research-phase of SpillwaveSolutions/agent-brain.
Open the folder on GitHubat commit 8339623
Gsd Research Phase next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Gsd Research Phase this skillSpillwaveSolutions/agent-brain | 119 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Logseq Review Workflow Evallogseq/logseq | 45k | — | ~1k | Automated safety check: Pass | AGPL-3.0 | |
| Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill | 2.5k | 2 repos | ~3.2k | Automated safety check: Pass | None | |
| Obsidian CLIAtmosphere/atmosphere | 3.8k | 13 repos | ~795 | Automated safety check: Pass | Apache-2.0 | |
| Esm Cjs Risk Scanlogseq/logseq | 45k | — | ~3.3k | Automated safety check: Pass | AGPL-3.0 | |
| Capture Conversationoutline/outline | 41k | — | ~474 | Automated safety check: Pass | Custom licence |
logseq/logseq
Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…
sdyckjq-lab/llm-wiki-skill
Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.
Atmosphere/atmosphere
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.
logseq/logseq
Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.
outline/outline
Save the current conversation, a decision, or a set of notes as a document in an Outline collection; use when the user wants to keep what was discussed in their knowledge base.
Astro-Han/karpathy-llm-wiki
A skill your agent uses when building or maintaining a personal LLM-powered knowledge base.
SpillwaveSolutions/agent-brain
Archive completed milestone and prepare for next version. An agent skill from SpillwaveSolutions/agent-brain.
SpillwaveSolutions/agent-brain
Modern Python coaching covering language foundations through advanced production patterns.
SpillwaveSolutions/agent-brain
Systematic debugging with persistent state across context resets
SpillwaveSolutions/agent-brain
Review and promote backlog items to active milestone. An agent skill from SpillwaveSolutions/agent-brain.
SpillwaveSolutions/agent-brain
Installation and configuration skill for Agent Brain document search system.
SpillwaveSolutions/agent-brain
Manage persistent context threads for cross-session work. An agent skill from SpillwaveSolutions/agent-brain.
Categories
Research how to implement a phase (standalone - usually use $gsd-plan-phase instead). Gsd Research Phase is an agent skill from SpillwaveSolutions/agent-brain.
Gsd Research Phase fits situations like: knowledge Management work in your project.
Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a claude-code`. Or copy the skill folder (.codex/skills/gsd-research-phase in SpillwaveSolutions/agent-brain) into .claude/skills/gsd-research-phase in your project. Claude Code loads it when a task matches its description.
Run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a codex`. Or copy the skill folder (.codex/skills/gsd-research-phase in SpillwaveSolutions/agent-brain) into .agents/skills/gsd-research-phase in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SpillwaveSolutions/agent-brain --skill gsd-research-phase -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gsd-research-phase, .gemini/skills/gsd-research-phase, .github/skills/gsd-research-phase and .opencode/skills/gsd-research-phase in your project.
Going by SKILL.md and its folder, Gsd Research Phase needs the command-line tools its instructions call (node).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Gsd Research Phase is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Gsd Research Phase: Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Esm Cjs Risk Scan (logseq/logseq, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
SpillwaveSolutions (a GitHub organization) maintains it in SpillwaveSolutions/agent-brain, which has 119 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 19, 2026.
Source: SpillwaveSolutions/agent-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.