research-wayfinder
From the author
Plans a research project as a durable decision map, resolving one design decision per session until the design is defensible and pre-registerable. Use at project start, when a design has more open decisions than one conversation holds, or when planning keeps restarting. Not for running analyses or writing the paper.
Install
npx skills add scdenney/open-science-skills --skill research-wayfinder -a claude-code
Installs to .claude/skills/research-wayfinder/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- wayfindertt-a1i/matt-skills-with-to-goalPlan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.Planning★ 187
- wayfinder-mapsrengwu/wayfinder-mapsPlan a huge chunk of work — more than one agent session can hold — as a shared map of investigation tickets, and resolve them one at a time until the way to the destination is clear.Finance★ 143
- research-routes-planzenx0x/allinlunaPlan software, research-exploration, or hybrid work from a repository, question, problem, frame, or arbitrary starting point. Use when Codex needs a route-neutral map, shared backbone, concurrent routes and branches, explicit claims and hypotheses, provenance, evidence polarity, lifecycle recovery, or a plan that keeps candidate inference separate from HumanDecision and canonical state.Science★ 63
- brainstormhashgraph-online/awesome-codex-pluginsExplore ideas, compare approaches, and produce a validated spec before planning. Use when the user describes what to build, asks how to approach something, proposes a new feature or design change, or needs to explore options before implementation.Planning★ 1.4K
- researchtestdouble/hanResearches an open-ended question — options, possible solutions, prior art, trade-offs, or how something works — and produces a durable, evidence-backed, adversarially-validated report that recommends an option without committing the team to any artifact. Use when you want to research approaches, weigh options, survey prior art or the state of the art, or understand how something works before committing to a direction. Does not diagnose a bug, failure, or root cause — use investigate. Does not specify a feature — use plan-a-feature. Does not create or update a coding standard — use coding-standard. Does not compare two concrete artifacts for gaps — use gap-analysis. Does not assess an existing module's architecture — use architectural-analysis. Does not capture feedback on Han's own skills — use han-feedback.Science★ 323
- research-craftnik1t7n/research-craft-skillUse when planning, reviewing, or improving research work: choosing research problems, designing ML/AI experiments, reading papers, building experiment loops, analyzing outputs, writing research notes, or turning vague curiosity into a disciplined research plan. Emphasizes avoiding absorbed problems, upgrading information inputs beyond shared reading lists, and reasoning backward from outcomes the researcher genuinely wants to exist.Science★ 50
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in