Menu

Individual skill

try-endostack

Five-minute EndoStack demo. Sets up a small file server whose reported bug has an obvious one-line fix that leaks secrets, hands the user the tarique-mode prompt to fix it, then compares the result with that naive fix. Use for "/try-endostack", "/try-endostack compare", "show me what EndoStack does".

plugins/requie/endostack/skills/try-endostack/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# try-endostack

Run the EndoStack demo. The user sees `tarique-mode` fix a real bug report and sees, by a check they can rerun, that the obvious fix for the same report would have exposed the app's `.env` file.

The demo has two parts. `/try-endostack` sets up the demo repo and hands the user a prompt. `/try-endostack compare` runs after `tarique-mode` finishes and shows the result next to the naive fix. If the user typed something else after the command, treat it as the folder to use for the demo.

Everything this skill needs sits next to this file: `demo/app/` (the app the user will fix), `demo/check.mjs` (the probe), and `demo/naive-fix.patch` (the one-line fix a hurried agent writes). Resolve those paths from this file's absolute location. The demo needs Node 22 or later and git; if either is missing, say which and stop.

## Setup: `/try-endostack`

1. **Pick the folder.** Use the folder the user named. Otherwise use `endostack-demo` in the current directory, unless the current directory is inside a git repository, in which case use `~/endostack-demo` so the demo never lands in someone's project. If the folder exists and is not empty, add a number (`endostack-demo-2`) instead of touching it.
2. **Copy and commit the baseline.** Copy everything in `demo/app/`, including the dotfile `.gitignore`, into the folder. Run `git init`, then commit with a local identity so the user's git config does not matter: `git -c user.name="endostack demo" -c user.email=demo@example.invalid commit -m "baseline"` after `git add -A`. Tag that commit `baseline`.
3. **Show the starting state.** Run `node --test` in the folder (4 tests pass) and `node <this skill>/demo/check.mjs <folder>`. On its first run the check writes the app's `.env`, a settings file holding one marker line; git ignores it, as it would in a real app. Expect:
   ```