Webapp Builder
sidequery/sidemantic
Build interactive analytics webapps, demos, dashboards, or embedded app surfaces from Sidemantic semantic models using copyable component primitives and deterministic query inspection.
Validate a txcript parsing, discovery, or search change against every real agent session on this machine — old-vs-new parity, no panics, and release-build timings.
Install Corpus Check
$ npx skills add skillsynchq/txcript --skill corpus-check -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install skillsynchq/txcript corpus-check --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/skillsynchq/txcript.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/corpus-check .claude/skills/corpus-check && 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 "corpus-check" agent skill from https://github.com/skillsynchq/txcript/tree/main/.claude/skills/corpus-check into .claude/skills/corpus-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corpus-check", 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/skillsynchq/txcript/tree/main/.claude/skills/corpus-checkType 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 skillsynchq/txcript --skill corpus-check -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install skillsynchq/txcript corpus-check --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skillsynchq/txcript.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/corpus-check .agents/skills/corpus-check && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "corpus-check" agent skill from https://github.com/skillsynchq/txcript/tree/main/.claude/skills/corpus-check into .agents/skills/corpus-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corpus-check", 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 skillsynchq/txcript --skill corpus-check -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install skillsynchq/txcript corpus-check --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skillsynchq/txcript.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/corpus-check .cursor/skills/corpus-check && 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 "corpus-check" agent skill from https://github.com/skillsynchq/txcript/tree/main/.claude/skills/corpus-check into .cursor/skills/corpus-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corpus-check", 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/skillsynchq/txcript.git --path .claude/skills/corpus-check--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 skillsynchq/txcript --skill corpus-check -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install skillsynchq/txcript corpus-check --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skillsynchq/txcript.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/corpus-check .gemini/skills/corpus-check && 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 "corpus-check" agent skill from https://github.com/skillsynchq/txcript/tree/main/.claude/skills/corpus-check into .gemini/skills/corpus-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corpus-check", 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 skillsynchq/txcript corpus-checkInstalls 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 skillsynchq/txcript --skill corpus-check -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/skillsynchq/txcript.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/corpus-check .github/skills/corpus-check && 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 "corpus-check" agent skill from https://github.com/skillsynchq/txcript/tree/main/.claude/skills/corpus-check into .github/skills/corpus-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corpus-check", 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 skillsynchq/txcript --skill corpus-check -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install skillsynchq/txcript corpus-check --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/skillsynchq/txcript.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/corpus-check .opencode/skills/corpus-check && 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 "corpus-check" agent skill from https://github.com/skillsynchq/txcript/tree/main/.claude/skills/corpus-check into .opencode/skills/corpus-check/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "corpus-check", 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.
Facts
- Skill name
corpus-check- GitHub stars
- 154
- Token cost
- ~827 tokens
- SKILL.md length
- 430 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Validate a txcript parsing, discovery, or search change against every real agent session on this machine — old-vs-new parity, no panics, and release-build timings.
- Works in 4 steps: Write a throwaway harness as an example… → Compare old vs new on identical inputs.… → Count failures explicitly. Unreadable… → …
- Tasks that involve App store release
- SKILL.md covers Procedure, Known traps (each cost real… and Report
- Calls git
What it does
Corpus Check is an agent skill from skillsynchq/txcript. Validate a txcript parsing, discovery, or search change against every real agent session on this machine — old-vs-new parity, no panics, and release-build timings. Use before landing changes to discover(), Store loaders, codecs, or the search index.
Its SKILL.md is about 830 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 Mobile, covering App store release. It works with Model Context Protocol, Rust and WebAssembly. The repository describes itself as: Pandoc for AI chats. Move ai chats across harnesses: Claude Code, Codex, OpenCode, Cursor, and more. Rust library, CLI, and WASM. The licence is Apache-2.0.
When your agent uses it
- Tasks that involve App store release
Example prompts
- “/corpus-check”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Write a throwaway harness as an example binary (examples/, modeled on
- Compare old vs new on identical inputs. Two options, cheapest first
- Count failures explicitly. Unreadable stores/sessions are skipped by
- Time it in release. --release only; report per-harness before/after
What it can do on your machine
Read from SKILL.md and the folder at commit 8cd3b0e. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Corpus Check loads about 827 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 430 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from skillsynchq/txcript at commit 8cd3b0e, republished under its Apache-2.0 licence (© skillsynchq). 430 words, ~827 tokens.
Download SKILL.mdSave it as
.claude/skills/corpus-check/SKILL.md (or your agent's skills folder).- name
- corpus-check
- description
- Validate a txcript parsing, discovery, or search change against every real agent session on this machine — old-vs-new parity, no panics, and release-build timings. Use before landing changes to discover(), Store loaders, codecs, or the search index.
- argument-hint
- what changed, e.g. "discover() fast path" or "index ordering"
Corpus check
Unit fixtures cover the shapes we thought of; the ~570 real sessions across
harnesses on this machine cover the shapes that actually exist. Any change to
discover(), a Store loader, a codec, or search::Index gets validated
against the full local corpus before it lands. This was done ad hoc twice
(discover-vs-load meta parity on Jul 6 2026; index determinism on Jul 9 2026)
— this skill is the distilled procedure.
Procedure
- Write a throwaway harness as an example binary (
examples/, modeled onexamples/search_bench.rs), not a test — it needs the real home-directory corpus, which tests must never touch. Delete it (or leave it untracked) when done unless the user wants it kept. - Compare old vs new on identical inputs. Two options, cheapest first:
- If the old behavior is reachable from the new code (e.g. full
load()vs the newdiscover()fast path), compare both paths in one binary. - Otherwise build a baseline binary from
main(git stash/git worktree) and diff the two binaries' outputs on the same corpus. Parity means field-level equality of the results (Metafields, message counts, hit ordering), not just "both succeeded". Report mismatches with session id + harness so they can be inspected individually.
- If the old behavior is reachable from the new code (e.g. full
- Count failures explicitly. Unreadable stores/sessions are skipped by
design in
local::sessions()— capture the skip count and check it didn't grow versus baseline. Zero panics is a hard gate (overflow checks are on in release for exactly this). - Time it in release.
--releaseonly; report per-harness before/after wall clock, since the corpus is dominated by one or two harnesses and an aggregate number hides regressions in the small ones.
Show full SKILL.md (160 more words)Show less
Known traps (each cost real debugging time)
- The current session mutates mid-scan. The session recording this very
run grows while you read it, so two enumerations differ. Exclude the live
session id, or scope comparisons with a harness/cwd filter that avoids it
(
--from <fixture-harness>was the Jul 9 fix). - Bookkeeping-only files have no real timestamp. Sessions with no
conversational records fall back to
Utc::now()forMeta.timestamp, so they "mismatch" between any two runs. Treat timestamp diffs on such files as expected; verify by checking the file has no conversational records before calling it a regression. - Fixture/synthetic sessions live in the corpus (greeting fixtures, cross-harness duplicates sharing one id). Ties and duplicates are where ordering nondeterminism hides — don't dedupe them away when checking determinism; run the pass twice and require identical output.
Report
State: corpus size per harness, parity result (mismatches with ids, or none), skip/failure counts vs baseline, per-harness timings before/after, and whether the throwaway harness was deleted or kept.
© skillsynchq, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/corpus-check of skillsynchq/txcript.
Open the folder on GitHubat commit 8cd3b0e
Compare with similar skills
Corpus Check 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 |
|---|---|---|---|---|---|---|
| Corpus Check this skillskillsynchq/txcript | 154 | — | ~827 | Automated safety check: Pass | Apache-2.0 | |
| Webapp Buildersidequery/sidemantic | 129 | — | ~5.5k | Automated safety check: Pass | AGPL-3.0 | |
| Build And Profilingpikax/verter | 112 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Creating Zed Extensionspr-pm/prpm | 122 | — | ~3.1k | Automated safety check: Notes | MIT | |
| Asc Revenuecat Catalog Syncrorkai/app-store-connect-cli-skills | 1.1k | 3 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Crossbindcrossbind/crossbind | 148 | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Build And Profiling
pikax/verter
Build dependency chains, rebuild sequences, profiling with MCP, and Analysis MCP server setup for Verter
Creating Zed Extensions
pr-pm/prpm
A skill your agent uses when creating Zed extensions with custom slash commands, language support, themes, or MCP servers - provides Rust/WASM extension structure, slash command API…
Asc Revenuecat Catalog Sync
rorkai/app-store-connect-cli-skills
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP.
Crossbind
crossbind/crossbind
A skill your agent uses when a user wants to call C++ or Rust from JavaScript or TypeScript; add a native library such as GDAL, SQLite, OpenSSL, GEOS or PROJ to a browser, Node.js, Cloudflare Worker…
Marionette Flutter Drive App
leancodepl/marionette_mcp
Set up and drive a running Flutter app (debug or profile) with Marionette — an AI agent's hands and eyes for the app.
More from skillsynchq/txcript
Harness
skillsynchq/txcript
Integrate a new AI coding-agent harness into txcript — native Body types, Codec, TextCodec, Store, wiring, and tests.
Release
skillsynchq/txcript
Cut a txcript release — dispatch the prepare-release workflow, approve the plan, watch the tag publish to crates.io, npm, and GitHub Releases, and verify.
Related
Works with
Categories
Questions about Corpus Check
What does Corpus Check do?
Validate a txcript parsing, discovery, or search change against every real agent session on this machine — old-vs-new parity, no panics, and release-build timings. Corpus Check is an agent skill from skillsynchq/txcript. Validate a txcript parsing, discovery, or search change against every real agent session on this machine — old-vs-new parity, no panics, and release-build timings.
When should I use Corpus Check?
Corpus Check fits situations like: tasks that involve App store release.
How do I install Corpus Check in Claude Code?
Run `npx skills add skillsynchq/txcript --skill corpus-check -a claude-code`. Or copy the skill folder (.claude/skills/corpus-check in skillsynchq/txcript) into .claude/skills/corpus-check in your project. Claude Code loads it when a task matches its description.
How do I install Corpus Check in Codex?
Run `npx skills add skillsynchq/txcript --skill corpus-check -a codex`. Or copy the skill folder (.claude/skills/corpus-check in skillsynchq/txcript) into .agents/skills/corpus-check in your project. Codex loads it when a task matches its description.
Can I use Corpus Check in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add skillsynchq/txcript --skill corpus-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/corpus-check, .gemini/skills/corpus-check, .github/skills/corpus-check and .opencode/skills/corpus-check in your project.
What does Corpus Check need to run?
Going by SKILL.md and its folder, Corpus Check needs the command-line tools its instructions call (git).
Does Corpus Check access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Corpus Check safe to install?
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.
What licence does Corpus Check use?
Corpus Check is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Corpus Check use?
About 827 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Corpus Check?
Skills that share tags, products or a category with Corpus Check: Webapp Builder (sidequery/sidemantic, 129 stars), Build And Profiling (pikax/verter, 112 stars), Creating Zed Extensions (pr-pm/prpm, 122 stars) and Asc Revenuecat Catalog Sync (rorkai/app-store-connect-cli-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Corpus Check?
skillsynchq (a GitHub organization) maintains it in skillsynchq/txcript, which has 154 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 29, 2026.
Source: skillsynchq/txcript on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.