Writing Livekit Scenarios
livekit-examples/agent-starter-python
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them.
Finds where an analogy breaks down before it's relied upon. An agent skill from human-avatar/skills-for-humanity.
$ npx skills add human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install human-avatar/skills-for-humanity s4h-analogy-boundary-testing --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/human-avatar/skills-for-humanity.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/s4h-analogy-boundary-testing .claude/skills/s4h-analogy-boundary-testing && 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 "s4h-analogy-boundary-testing" agent skill from https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-analogy-boundary-testing into .claude/skills/s4h-analogy-boundary-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "s4h-analogy-boundary-testing", 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/human-avatar/skills-for-humanity/tree/main/skills/s4h-analogy-boundary-testingType 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 human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install human-avatar/skills-for-humanity s4h-analogy-boundary-testing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/s4h-analogy-boundary-testing .agents/skills/s4h-analogy-boundary-testing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "s4h-analogy-boundary-testing" agent skill from https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-analogy-boundary-testing into .agents/skills/s4h-analogy-boundary-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "s4h-analogy-boundary-testing", 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 human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install human-avatar/skills-for-humanity s4h-analogy-boundary-testing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/s4h-analogy-boundary-testing .cursor/skills/s4h-analogy-boundary-testing && 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 "s4h-analogy-boundary-testing" agent skill from https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-analogy-boundary-testing into .cursor/skills/s4h-analogy-boundary-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "s4h-analogy-boundary-testing", 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/human-avatar/skills-for-humanity.git --path skills/s4h-analogy-boundary-testing--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 human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install human-avatar/skills-for-humanity s4h-analogy-boundary-testing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/s4h-analogy-boundary-testing .gemini/skills/s4h-analogy-boundary-testing && 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 "s4h-analogy-boundary-testing" agent skill from https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-analogy-boundary-testing into .gemini/skills/s4h-analogy-boundary-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "s4h-analogy-boundary-testing", 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 human-avatar/skills-for-humanity s4h-analogy-boundary-testingInstalls 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 human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/s4h-analogy-boundary-testing .github/skills/s4h-analogy-boundary-testing && 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 "s4h-analogy-boundary-testing" agent skill from https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-analogy-boundary-testing into .github/skills/s4h-analogy-boundary-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "s4h-analogy-boundary-testing", 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 human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install human-avatar/skills-for-humanity s4h-analogy-boundary-testing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/human-avatar/skills-for-humanity.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/s4h-analogy-boundary-testing .opencode/skills/s4h-analogy-boundary-testing && 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 "s4h-analogy-boundary-testing" agent skill from https://github.com/human-avatar/skills-for-humanity/tree/main/skills/s4h-analogy-boundary-testing into .opencode/skills/s4h-analogy-boundary-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "s4h-analogy-boundary-testing", 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.
s4h-analogy-boundary-testingFinds where an analogy breaks down before it's relied upon. An agent skill from human-avatar/skills-for-humanity.
S4h Analogy Boundary Testing is an agent skill from human-avatar/skills-for-humanity. Finds where an analogy breaks down before it's relied upon. Analogies fail silently — the damage happens when decisions are made on a mapping that doesn't hold in the relevant dimension. Triggers: 'stress-test this analogy', 'where does this comparison break', 'does this really apply', 'test the metaphor', 'where is the analogy wrong'.
Its SKILL.md is about 1.4k 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 Testing & QA, covering Load testing. The repository describes itself as: Structured reasoning methodologies from history's most rigorous thinkers, packaged as Claude Code skills. The licence is MIT.
Read from SKILL.md and the folder at commit a30df8b. 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.
No scripts in the folder and no shell commands in SKILL.md.
From 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.
S4h Analogy Boundary Testing loads about 1.4k tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 687 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 human-avatar/skills-for-humanity at commit a30df8b, republished under its MIT licence (© human-avatar). 687 words, ~1,351 tokens.
.claude/skills/s4h-analogy-boundary-testing/SKILL.md (or your agent's skills folder).Analogies are tools, not truths. The danger is not using an analogy — it is using one past its boundary. Analogies fail silently: the flaw is invisible until a decision has been made that depended on the part that didn't hold. This skill finds the boundary before that happens.
Step 1: State the Analogy Write it explicitly: "X is like Y." Name the analogy being tested, the domain it comes from, and the claim being made on the basis of it.
Framing check: Confirm the specific analogy before continuing. State what you've identified — the source domain, target domain, and the claim being made — in one sentence, then use AskUserQuestion:
Step 2: List Similarities What does the analogy capture correctly? List every genuine parallel — the aspects where the structural correspondence is real. This is not validation; it's establishing what the analogy is good for before finding what it isn't.
Step 3: List Differences Every meaningful divergence between X and Y is a potential failure point. List them systematically: different actors, different dynamics, different constraints, different feedback mechanisms, different scales, different reversibility. Be thorough — incomplete difference-listing is the most common failure mode here.
Step 4: Test Each Difference Against the Decision
Before narrowing: Show the complete list of differences from Step 3 to the user first. Use AskUserQuestion:
For each decision or conclusion being made on the basis of this analogy: which differences are relevant to that specific decision? A difference that doesn't affect the conclusion is harmless. A difference that does affect it invalidates the reasoning.
Step 5: Does the Conclusion Still Hold? For each relevant difference identified in Step 4: if this difference is real, does the conclusion derived from the analogy still follow? If not, the analogy cannot support that conclusion.
Step 6: State Safe Scope Where can this analogy be validly relied upon? What does it illuminate, and what decisions can it inform? State the boundary clearly.
Before proceeding, use the AskUserQuestion tool. State your interpretation of the situation in 1–2 sentences — what is being analyzed and what the core question is — then ask:
Proceed based on their selection. If the user reframes, incorporate the correction before running any analysis.
Analogy: [X is like Y — domain and claim]
Similarities (what the analogy captures correctly):
[Bulleted list]
Differences (potential failure points):
[Bulleted list — be thorough]
Relevant differences for this decision:
| Difference | Relevant to decision? | Effect on conclusion |
|---|---|---|
Conclusion validity:
[Does the analogy support the conclusion? Yes / Partially / No — with reason]
Safe scope — what this analogy validly applies to:
[Bounded statement]
The most useful output is the safe scope statement — a positive claim about where the analogy is reliable. Discarding an analogy entirely because it has limits wastes the genuine insight it contains.
After delivering this output, use AskUserQuestion to offer the next move:
/s4h-analogy-domain-transfer — Now that boundaries are clear, execute the transfer carefully/s4h-logic-check — Check whether conclusions crossed a boundary they shouldn't have/s4h-constraint-hardness-testing — Are the boundary differences hard constraints or soft?© human-avatar, 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 skills/s4h-analogy-boundary-testing of human-avatar/skills-for-humanity.
Open the folder on GitHubat commit a30df8b
S4h Analogy Boundary Testing 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 |
|---|---|---|---|---|---|---|
| S4h Analogy Boundary Testing this skillhuman-avatar/skills-for-humanity | 231 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Writing Livekit Scenarioslivekit-examples/agent-starter-python | 264 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Go Testingcxuu/golang-skills | 173 | 1 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Goalcraftgrp06/goalcraft | 102 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Thinking Partnermattnowdev/thinking-partner | 206 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Visionkunchenguid/vision | 331 | — | ~2.9k | Automated safety check: Pass | MIT |
livekit-examples/agent-starter-python
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them.
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
grp06/goalcraft
Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work.
mattnowdev/thinking-partner
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.
kunchenguid/vision
Draft and stress-test a VISION.md for a repository, then iterate with the author on an interactive review board until approved.
owenHochwald/volt
Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons.
human-avatar/skills-for-humanity
Takes a situation described in plain English, designs a short sequence of reasoning skills for it and runs them in order, each building on the last.
human-avatar/skills-for-humanity
Runs a decision or policy question past five ethical frameworks, has them review one another, and returns a chair's synthesis of which values conflict.
human-avatar/skills-for-humanity
Run a reasoning problem, argument, plan, or decision through a council of 5 logical reasoning advisors who analyze it from distinct reasoning frameworks, peer-review each other, and synthesize a…
human-avatar/skills-for-humanity
Entry point for the aesthetic toolkit. An agent skill from human-avatar/skills-for-humanity.
human-avatar/skills-for-humanity
Tests whether the parts of something form a unified whole — finding the jarring inconsistencies that accumulate when different contributors work without a shared vision.
human-avatar/skills-for-humanity
Tests whether a solution is more complex than it needs to be — distinguishing necessary complexity from accidental complexity that accreted over time.
Categories
Finds where an analogy breaks down before it's relied upon. An agent skill from human-avatar/skills-for-humanity. S4h Analogy Boundary Testing is an agent skill from human-avatar/skills-for-humanity. Finds where an analogy breaks down before it's relied upon.
S4h Analogy Boundary Testing fits situations like: tasks that involve Load testing.
Run `npx skills add human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a claude-code`. Or copy the skill folder (skills/s4h-analogy-boundary-testing in human-avatar/skills-for-humanity) into .claude/skills/s4h-analogy-boundary-testing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a codex`. Or copy the skill folder (skills/s4h-analogy-boundary-testing in human-avatar/skills-for-humanity) into .agents/skills/s4h-analogy-boundary-testing 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 human-avatar/skills-for-humanity --skill s4h-analogy-boundary-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/s4h-analogy-boundary-testing, .gemini/skills/s4h-analogy-boundary-testing, .github/skills/s4h-analogy-boundary-testing and .opencode/skills/s4h-analogy-boundary-testing in your project.
SKILL.md names no scripts, command-line tools or credentials: S4h Analogy Boundary Testing is instructions for the agent only.
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.
S4h Analogy Boundary Testing 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.4k tokens (SKILL.md is roughly 5.4k 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 S4h Analogy Boundary Testing: Writing Livekit Scenarios (livekit-examples/agent-starter-python, 264 stars), Go Testing (cxuu/golang-skills, 173 stars), Goalcraft (grp06/goalcraft, 102 stars) and Thinking Partner (mattnowdev/thinking-partner, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
human-avatar (a GitHub organization) maintains it in human-avatar/skills-for-humanity, which has 231 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on July 15, 2026.
Source: human-avatar/skills-for-humanity on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.