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.
Agent skill
Soctheory Argument Development
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid, warranted argument that survives rival theories and…
Install Soctheory Argument Development
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soctheory-argument-development --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/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Sociological-Theory-Skills/skills/soctheory-argument-development .claude/skills/soctheory-argument-development && 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 "soctheory-argument-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Sociological-Theory-Skills/skills/soctheory-argument-development into .claude/skills/soctheory-argument-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soctheory-argument-development", 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/brycewang-stanford/Awesome-Journal-Skills/tree/main/Sociological-Theory-Skills/skills/soctheory-argument-developmentType 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 brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soctheory-argument-development --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Sociological-Theory-Skills/skills/soctheory-argument-development .agents/skills/soctheory-argument-development && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "soctheory-argument-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Sociological-Theory-Skills/skills/soctheory-argument-development into .agents/skills/soctheory-argument-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soctheory-argument-development", 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 brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soctheory-argument-development --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Sociological-Theory-Skills/skills/soctheory-argument-development .cursor/skills/soctheory-argument-development && 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 "soctheory-argument-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Sociological-Theory-Skills/skills/soctheory-argument-development into .cursor/skills/soctheory-argument-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soctheory-argument-development", 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/brycewang-stanford/Awesome-Journal-Skills.git --path Sociological-Theory-Skills/skills/soctheory-argument-development--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 brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soctheory-argument-development --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Sociological-Theory-Skills/skills/soctheory-argument-development .gemini/skills/soctheory-argument-development && 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 "soctheory-argument-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Sociological-Theory-Skills/skills/soctheory-argument-development into .gemini/skills/soctheory-argument-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soctheory-argument-development", 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 brycewang-stanford/Awesome-Journal-Skills soctheory-argument-developmentInstalls 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 brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Sociological-Theory-Skills/skills/soctheory-argument-development .github/skills/soctheory-argument-development && 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 "soctheory-argument-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Sociological-Theory-Skills/skills/soctheory-argument-development into .github/skills/soctheory-argument-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soctheory-argument-development", 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 brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soctheory-argument-development --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Sociological-Theory-Skills/skills/soctheory-argument-development .opencode/skills/soctheory-argument-development && 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 "soctheory-argument-development" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Sociological-Theory-Skills/skills/soctheory-argument-development into .opencode/skills/soctheory-argument-development/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soctheory-argument-development", 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
soctheory-argument-development- GitHub stars
- 1.2k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 566 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid, warranted argument that survives rival theories and…
- Works in 5 steps: Premise check. Are the starting premises… → Inference check. Does each proposition… → Warrant check. For each major claim,… → …
- Stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid
- SKILL.md covers When to trigger, The argument audit, Toulmin per proposition and Handling rivals without data, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Soctheory Argument Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid, warranted argument that survives rival theories and counter-cases. Develops and audits the argument; it does NOT define the concepts (soctheory-theory-construction) or bound the theory's domain (soctheory-boundary-conditions).
Its SKILL.md is about 1.2k 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: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid
- Warranted argument that survives rival theories and counter-cases
Example prompts
- “/soctheory-argument-development”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Premise check. Are the starting premises stated, defensible, and consistent with the
- Inference check. Does each proposition actually follow from the premises + mechanism?
- Warrant check. For each major claim, state the warrant: *why is this a good reason to
- Rival-theory check. Name the strongest rival explanation and show, on theoretical
- Counter-case / hard-case check. Construct the case where your theory would seem to fail.
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. 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
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.
Network
No URLs in SKILL.md.
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
Soctheory Argument Development loads about 1.2k tokens when it runs. Until then it costs about 95 tokens; SKILL.md has 566 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 brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 566 words, ~1,223 tokens.
Download SKILL.mdSave it as
.claude/skills/soctheory-argument-development/SKILL.md (or your agent's skills folder).- name
- soctheory-argument-development
- description
- Use when stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid, warranted argument that survives rival theories and counter-cases. Develops and audits the argument; it does NOT define the concepts (soctheory-theory-construction) or bound the theory's domain (soctheory-boundary-conditions).
Argument Development: Warrants, Rivals, Validity (soctheory-argument-development)
When to trigger
- Concepts and propositions exist, but the reasoning that connects them is thin
- A reviewer would say "the propositions don't follow from the premises"
- You have not engaged the obvious rival explanation
- The argument has not been tested against a counter-case or a hard case
At ST, logical soundness plays the role statistics play at empirical journals. The argument is the evidence. This skill makes it valid before reviewers find the gaps.
The argument audit
Walk the manuscript's spine — premises → mechanism → propositions → conclusion — and check each link. Reed's "Justifying Sociological Knowledge" (ST 2008, 26(2):101–129) frames the central demand: every theoretical claim carries an implicit warrant, and you owe the reader the warrant, not just the claim.
- Premise check. Are the starting premises stated, defensible, and consistent with the
assumptions from
soctheory-theory-construction? An unstated premise is a hidden bet. - Inference check. Does each proposition actually follow from the premises + mechanism? Name the inference type — deductive derivation, abduction (the "best explanation" move central to ST theorizing; cf. Timmermans & Tavory, ST 2012, 30(3):167–186), or analogy — and check it is doing legitimate work.
- Warrant check. For each major claim, state the warrant: why is this a good reason to believe the claim? If the warrant is "it seems plausible," it is not yet an argument.
- Rival-theory check. Name the strongest rival explanation and show, on theoretical grounds, why yours is better (more parsimonious, more general, dissolves an anomaly the rival cannot). Defeating a strawman convinces no one.
- Counter-case / hard-case check. Construct the case where your theory would seem to fail.
Either the argument handles it, or you have found a boundary condition (hand to
soctheory-boundary-conditions).
Toulmin per proposition
A compact discipline for each load-bearing proposition:
- Claim — the proposition.
- Grounds — the concepts/premises it rests on.
- Warrant — why the grounds support the claim (the mechanism does most of this work).
- Backing — the tradition or prior reasoning that licenses the warrant.
- Rebuttal — the condition under which the claim would not hold (a candidate boundary condition).
A proposition that cannot fill warrant and rebuttal is an assertion, not a theoretical claim.
Show full SKILL.md (210 more words)Show less
Handling rivals without data
Because ST does not test, you adjudicate rivals theoretically:
| Rival situation | Theoretical move |
|---|---|
| Rival explains the same cases | Show your account is more parsimonious or unifies more |
| Rival rests on a shakier premise | Expose and challenge that premise |
| Rival and yours seem observationally equivalent | Specify a conceptual difference that matters, even if untested |
| Rival is a special case of yours | Subsume it and show the added range |
Checklist
- The premises are stated and consistent with the theory's assumptions
- Each proposition demonstrably follows from premises + mechanism (inference type named)
- Each load-bearing claim states its warrant (not "it seems plausible")
- The strongest rival theory is named and answered on theoretical grounds
- At least one counter-case / hard case is constructed and handled (or yields a boundary condition)
- No empirical "test" stands in for an argument; data, if any, only illustrates
Anti-patterns
- A chain of plausible-sounding claims with no stated warrants
- Engaging a strawman rival instead of the strongest one
- "Future research could test this" used to dodge a current logical gap
- Abduction invoked as a license to assert rather than to reason toward the best explanation
- Inconsistency: a later proposition silently violating an earlier premise
- Smuggling an empirical result in as if it settled a theoretical dispute
Output format
【Spine】premises → mechanism → propositions → conclusion: valid? [Y/N + gaps]
【Warrants stated】per load-bearing claim: yes / missing [...]
【Strongest rival】[named] → why yours wins (theoretically)
【Counter-case】[case] → handled / becomes a boundary condition
【Inference types】deductive / abductive / analogical — each legitimate?
【Next step】soctheory-boundary-conditions© brycewang-stanford, MIT. 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 Sociological-Theory-Skills/skills/soctheory-argument-development of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Soctheory Argument Development 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 |
|---|---|---|---|---|---|---|
| Soctheory Argument Development this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.2k | 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 | 172 | 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 |
Similar skills
Go Testing
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.
Goalcraft
grp06/goalcraft
Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work.
Thinking Partner
mattnowdev/thinking-partner
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.
Vision
kunchenguid/vision
Draft and stress-test a VISION.md for a repository, then iterate with the author on an interactive review board until approved.
Volt Load Testing
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.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Soctheory Argument Development
What does Soctheory Argument Development do?
A skill your agent uses when stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid, warranted argument that survives rival theories and…. Soctheory Argument Development is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid, warranted argument that survives rival theories and counter-cases.
When should I use Soctheory Argument Development?
Soctheory Argument Development fits situations like: stress-testing the reasoning of a Sociological Theory (ST) manuscript — turning stated propositions into a valid; warranted argument that survives rival theories and counter-cases.
How do I install Soctheory Argument Development in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a claude-code`. Or copy the skill folder (Sociological-Theory-Skills/skills/soctheory-argument-development in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/soctheory-argument-development in your project. Claude Code loads it when a task matches its description.
How do I install Soctheory Argument Development in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a codex`. Or copy the skill folder (Sociological-Theory-Skills/skills/soctheory-argument-development in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/soctheory-argument-development in your project. Codex loads it when a task matches its description.
Can I use Soctheory Argument Development 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 brycewang-stanford/Awesome-Journal-Skills --skill soctheory-argument-development -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/soctheory-argument-development, .gemini/skills/soctheory-argument-development, .github/skills/soctheory-argument-development and .opencode/skills/soctheory-argument-development in your project.
What does Soctheory Argument Development need to run?
SKILL.md names no scripts, command-line tools or credentials: Soctheory Argument Development is instructions for the agent only.
Does Soctheory Argument Development access the network?
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.
Is Soctheory Argument Development 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 Soctheory Argument Development use?
Soctheory Argument Development is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Soctheory Argument Development use?
About 1.2k tokens (SKILL.md is roughly 4.9k 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 Soctheory Argument Development?
Skills that share tags, products or a category with Soctheory Argument Development: Writing Livekit Scenarios (livekit-examples/agent-starter-python, 264 stars), Go Testing (cxuu/golang-skills, 172 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.
Who maintains Soctheory Argument Development?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.