Thinkweave bootstrap
Install or diagnose ThinkWeave under Codex, especially on native Windows when weave is missing, resolves but cannot import, or is blocked by the sandbox.From its SKILL.md
npx -y skills add marekpal97/thinkweave --skill thinkweave-bootstrapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
ThinkWeave Bootstrap
Run the read-only diagnostic first, from the ThinkWeave checkout directory —
this route needs nothing on PATH, so it also works when weave itself is the
thing that is missing:
uv run --project . weave doctor --mcp
If weave is missing or cannot import under the Codex sandbox, ask permission
to run the existing checkout's installer outside that restriction — again from
the checkout directory, and again without relying on weave resolving:
uv run --project . weave install --yes --harness codex
The installer performs the dependency sync once, writes a native-Windows
launcher that uses module execution without live uv synchronization or the
editable .pth, and makes that launcher available on the user PATH. Restart
Codex after installation, then run the doctor again.
If weave still does not resolve after that restart, sign out of Windows and
back in once: the installer broadcasts the PATH change, but a process that
never re-reads its environment keeps the PATH it was launched with.
Do not silently substitute FTS when the doctor reports that semantic retrieval is unavailable; surface that as a separate retrieval failure.