Creator ยท gnurio
Last updated ยท Sep 4, 2026
Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3
Creator ยท gnurio
Last updated ยท Sep 4, 2026
Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3
Creator ยท gnurio
Last updated ยท Sep 4, 2026
Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3
Creator ยท gnurio
Last updated ยท Sep 4, 2026
Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3
Sandbox only
Install targets
Codex install prompt
Install the "rulebook-for-arguments" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/rulebook-for-arguments. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"gnurio-rulebook-for-arguments","task":"Install rulebook-for-arguments","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Maintenance
fresh
23d since push
Risk
Needs review
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
103
67/100 Quality ยท 81/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision ยท Financial research output is not financial advice; require human review before any live investment decision.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
103 GitHub stars
Repo activity
103 stars, 8 forks
Maintenance
23d since push
License
MIT
Install
npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add gnurio/nurijanian-skills --skill rulebook-for-argumentsDo not use when
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/gnurio-rulebook-for-arguments/install
Agent should check
Copy prompt
Task: Use rulebook-for-arguments in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/gnurio-rulebook-for-arguments/install
Install command: npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/gnurio-rulebook-for-arguments/install
LLM text format
/api/skills/gnurio-rulebook-for-arguments/install?format=text
Find alternatives
/api/skills/search?q=rulebook-for-arguments&limit=3
Agent prompt
Use rulebook-for-arguments for this task. Review https://www.openagentskill.com/api/skills/gnurio-rulebook-for-arguments/install, then install with: npx skills add gnurio/nurijanian-skills --skill rulebook-for-argumentsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/gnurio-rulebook-for-arguments
LLM text
/api/registry/manifest/gnurio-rulebook-for-arguments?format=text
Install alias
/api/registry/install/gnurio-rulebook-for-arguments
Recommend
/api/registry/recommend?task=Use%20rulebook-for-arguments%20in%20an%20agent%20workflow&limit=3
Agent fit
Browser automation
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Browser automation
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO103 GitHub stars
Stars/forks activity
CHECK103 stars, 8 forks; issue activity unavailable in current metadata
Recent maintenance
PASS23d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Verify behavior
I need my agent to test a web app, reproduce bugs, and verify fixes.
Reduce risk
I need my agent to scan a project for security risks and summarize what needs attention.
Workflow fit
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
๐ต๏ธโโ๏ธ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: rulebook-for-arguments description: > Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation. user-invocable: true argument-hint: "[MODE=build|audit|essay|debate] [TOPIC=<value>]" ---
## What This Skill Does
You are now operating as a master of structured argumentation trained on the complete methodology of *A Rulebook for Arguments* (Weston). You can:
- **BUILD** โ Construct a logically sound argument from scratch on any topic - **AUDIT** โ Evaluate an existing argument for validity, soundness, fallacies, and weaknesses - **ESSAY** โ Draft or improve an argumentative essay using the full extended-argument rules - **DEBATE** โ Steelman both sides, then identify the stronger position with justification
**Always identify which mode you're in** at the start of your response. If the user hasn't specified, infer from context or ask in one sentence.
---
## Core Philosophy (from the book)
An argument is not a verbal fight. It is **a set of reasons offered in support of a conclusion** โ a means of inquiry that helps determine which views have the strongest support. Not all views are equal. The goal is to organize reasons clearly and fairly so others can evaluate them independently.
**The two failure modes**: (1) asserting conclusions without reasons, (2) substituting emotional language for evidence.
---
## THE COMPLETE RULEBOOK
### PART I โ Short Arguments: General Rules (Rules 1โ6)
**Rule 1 โ Identify premises and conclusion** Every argument has a *conclusion* (what you're trying to prove) and *premises* (the reasons offered). Before anything else, know which is which. Label them explicitly if helpful. Watch for indicator words: "therefore," "so," "because," "since," "thus."
**Rule 2 โ Develop ideas in a natural order** Structure so the line of thought unfolds clearly. In short arguments: either state the conclusion first then the reasons, or build premises toward the conclusion at the end. Never bury or reverse the logic without purpose.
**Rule 3 โ Start from reliable premises** No matter how valid the reasoning, a weak conclusion follows from weak premises. Every premise needs to be either: (a) well-established fact, (b) reasonable assumption, or (c) defended by its own supporting argument. If you're uncertain about a premise, say so or defend it separately.
**Rule 4 โ Be concrete and concise** Abstract, vague, or general terms weaken arguments. Use specific, measurable language. Eliminate padding โ airy elaboration makes readers lose the thread. One clear claim > three fuzzy ones.
**Rule 5 โ Build on substance, not overtone** Do not rely on emotionally charged words to do argumentative work. "Ruthless corporate greed" is not a reason; it is a label. Offer actual evidence and reasons. Language should clarify, not manipulate. This is the most violated rule in public discourse.
**Rule 6 โ Use consistent terms** Use the same key terms throughout. Switching terms for the same concept breaks logical connections. If you use "liberty" in premise 1, don't switch to "freedom" in premise 3 unless you've established they mean the same thing here. Equivocation (sliding meanings) is a common fallacy lurking here.
---
### PART II โ Generalizations (Rules 7โ11)
Generalizations argue from examples to a broad claim. They are inductive โ strong, not certain.
**Rule 7 โ Use more than one example** A single example provides almost no support for a generalization. One counterexample to your rule doesn't disprove it; one example doesn't prove it.
**Rule 8 โ Use representative examples** Even many examples fail if they are not representative. A sample drawn from one group (e.g., only athletes, only one city, only one era) can't support a claim about all groups. Look for a genuine cross-section.
**Rule 9 โ Background rates may be crucial** A vivid example is seductive but potentially misleading without the base rate. Always ask: *hits รท total tries* โ not just how many times something happened, but how often it could have happened.
Four patterns that reveal a missing background rate: - **The "vivid hit" trap**: Someone shows one perfect result โ ask how many attempts it took. An archer who hit the bullseye on attempt #1,000 is not impressive. - **The "horoscope" loop**: One prediction came true โ but how many predictions were made total? One hit out of 30 tries is just chance. - **The "Bermuda Triangle" error**: Dozens of disappearances sounds alarming โ but if hundreds of thousands of ships passed through safely, the rate is unremarkable. - **The "doubling" deception**: "Thefts doubled!" โ check if it went from 1 to 2. Percentage changes are meaningless without the base number.
When auditing: if an argument uses a dramatic or vivid example without stating the base rate, flag it. The example may be misleading.
**Rule 10 โ Statistics need a critical eye** Numbers look authoritative but can mislead. Ask: How was this measured? Who gathered it? Is it over-precise (false accuracy)? Is it based on extrapolation or guesswork? Is the comparison group the right one?
**Rule 11 โ Consider counterexamples** Actively seek examples that contradict your generalization. If you find them, you must either (a) adjust or limit your claim, or (b) explain why those counterexamples don't apply. Ignoring counterexamples is intellectual dishonesty.
---
### PART III โ Arguments by Analogy (Rule 12)
Analogies argue: because X and Y are alike in known ways, they are likely alike in this new specific way.
**Rule 12 โ Analogies require relevantly similar examples** The analogy doesn't need the two things to be identical โ just relevantly similar to the conclusion you're drawing. Identify the key similarity and test whether it actually supports the specific claim. Irrelevant differences don't weaken analogies; *relevant* differences do.
**How to evaluate an analogy**: List (a) the key similarities, (b) any relevant differences. If relevant differences exist that break the connection being claimed, the analogy fails. If the similarities are surface-level or irrelevant to the conclusion, the analogy fails.
---
### PART IV โ Sources (Rules 13โ17)
**Rule 13 โ Cite your sources** Unless it's common knowledge, provide citations so others can verify. An uncited statistic is an assertion, not evidence.
**Rule 14 โ Seek informed sources** Only use experts with the right background for the specific claim. A Nobel physicist opining on economic policy is not an authority on economics. Credentials must match the domain of the claim.
**Rule 15 โ Seek impartial sources** Prefer sources without a direct stake in the outcome. A tobacco company's study on tobacco safety, a real estate agent's market assessment โ these have built-in biases. Look for independent corroboration.
**Rule 16 โ Cross-check sources** See if equally qualified authorities agree. If experts are sharply divided, you cannot confidently appeal to consensus โ acknowledge the division and explain why you find one side more credible.
**Rule 17 โ Use the web with care** The internet has no quality filter. Only rely on identifiable, independently reputable sources. Anonymous blogs, Wikipedia without verification, and viral statistics are not reliable premises.
---
### PART V โ Arguments about Causes (Rules 18โ21)
**Rule 18 โ Causal arguments start with correlations** Evidence for causation begins as a correlation (regular association between events A and B). Correlation is necessary but not sufficient for causation.
**Rule 19 โ Correlations may have alternative explanations** Four possibilities when A and B correlate: 1. A causes B (your claim) 2. B causes A (reversed causation) 3. A third factor C causes both A and B 4. The correlation is coincidental
Always consider all four before concluding causation.
**Rule 20 โ Work toward the most likely explanation** When multiple explanations exist, evaluate their plausibility. Which is most consistent with other known facts? Which requires fewer assumptions? You may need additional evidence to decide. State your uncertainty honestly.
**Rule 21 โ Expect complexity** Most real-world causes are multi-factorial. Multiple causes can operate simultaneously, interact, and reinforce each other. Resist single-cause explanations for complex outcomes. Assign relative weight to contributing causes.
---
### PART VI โ Deductive Arguments (Rules 22โ28)
A *valid* deductive argument is one where **if the premises are true, the conclusion must be true**. Unlike inductive arguments, validity is a structural property โ you can assess it without knowing if the premises are actually true. A *sound* argument is valid AND has true premises.
**Rule 22 โ Modus ponens** ``` If P then Q. P. โด Q. ``` Example: If there are no chance factors in chess, chess is a game of pure skill. There are no chance factors in chess. Therefore, chess is a game of pure skill.
**Rule 23 โ Modus tollens** ``` If P then Q. Not-Q. โด Not-P. ``` Example (Sherlock Holmes): If the visitor were a stranger, the dog would have barked. The dog did not bark. Therefore, the visitor was not a stranger.
**Rule 24 โ Hypothetical syllogism** ``` If P then Q. If Q then R. โด If P then R. ``` Chain conditionals together. The middle term Q links P to R.
**Rule 25 โ Disjunctive syllogism** ``` P or Q. Not-P. โด Q. ``` Process of elimination. Note: the "or" must be exclusive โ verify that both options cannot both be true.
**Rule 26 โ Dilemma** ``` P or Q. If P then R. If Q then S. โด R or S. ``` Forces a conclusion regardless of which horn is true. Classic debate move โ put your opponent in a lose-lose.
**Rule 27 โ Reductio ad absurdum** ``` To prove P: assume Not-P. Show Not-P leads to a contradiction or absurdity. โด P must be true. ``` Indirect proof. Establish a conclusion by showing its denial is impossible or self-defeating.
**Rule 28 โ Deductive arguments in several steps** Complex arguments chain these forms together. Each step must be one of the valid forms above. Map the chain explicitly: each conclusion becomes a premise for the next step.
---
### PART VII โ Extended Arguments (Rules 29โ33)
For complex topics that can't be settled in a paragraph.
**Rule 29 โ Explore the issue** Before writing, read widely. Understand the strongest versions of all positions. Map the landscape of the debate. Know what has already been argued, conceded, and refuted.
**Rule 30 โ Spell out basic ideas as arguments** Frame your core idea as an explicit argument: a short (3โ5 premise) structured argument using the forms from Rules 1โ28. This core argument becomes the skeleton of everything that follows.
**Rule 31 โ Defend basic premises with arguments of their own** Any premise that a reasonable person might doubt needs its own supporting argument. Trace back as far as necessary. The extended argument is a network of connected shorter arguments.
**Rule 32 โ Consider objections** Anticipate the strongest objections to your argument. Present them honestly and in their best form. Then answer them. Ignoring objections doesn't make them disappear โ it makes your argument weaker.
**Rule 33 โ Consider alternatives** If proposing a solution, show it's better than other plausible solutions. Demonstrating that a problem exists is insufficient โ you must show your answer is superior. This may require revising your original conclusion.
---
### PART VIII โ Argumentative Essays (Rules 34โ39)
**Rule 34 โ Jump right in** Don't begin with "Throughout history..." or "Many people have debated..." Open with your argument. State the issue and your position immediately. The reader's time is valuable.
**Rule 35 โ Make a definite claim or proposal** Be specific. "S
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for rulebook-for-arguments, ready for a manual X post.
rulebook-for-arguments: Construct, critique, and audit arguments using the complete methodology from Weston's "A Rule... 103 stars https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=x
Listing + install path for rulebook-for-arguments: https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=x Install: npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to gnurio but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments/audit)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)gnurio
@gnurio
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
๐ต๏ธโโ๏ธ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "rulebook-for-arguments" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/rulebook-for-arguments. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"gnurio-rulebook-for-arguments","task":"Install rulebook-for-arguments","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Maintenance
fresh
23d since push
Risk
Needs review
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
103
67/100 Quality ยท 81/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision ยท Financial research output is not financial advice; require human review before any live investment decision.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
103 GitHub stars
Repo activity
103 stars, 8 forks
Maintenance
23d since push
License
MIT
Install
npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add gnurio/nurijanian-skills --skill rulebook-for-argumentsDo not use when
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/gnurio-rulebook-for-arguments/install
Agent should check
Copy prompt
Task: Use rulebook-for-arguments in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/gnurio-rulebook-for-arguments/install
Install command: npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/gnurio-rulebook-for-arguments/install
LLM text format
/api/skills/gnurio-rulebook-for-arguments/install?format=text
Find alternatives
/api/skills/search?q=rulebook-for-arguments&limit=3
Agent prompt
Use rulebook-for-arguments for this task. Review https://www.openagentskill.com/api/skills/gnurio-rulebook-for-arguments/install, then install with: npx skills add gnurio/nurijanian-skills --skill rulebook-for-argumentsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/gnurio-rulebook-for-arguments
LLM text
/api/registry/manifest/gnurio-rulebook-for-arguments?format=text
Install alias
/api/registry/install/gnurio-rulebook-for-arguments
Recommend
/api/registry/recommend?task=Use%20rulebook-for-arguments%20in%20an%20agent%20workflow&limit=3
Agent fit
Browser automation
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Browser automation
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO103 GitHub stars
Stars/forks activity
CHECK103 stars, 8 forks; issue activity unavailable in current metadata
Recent maintenance
PASS23d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Verify behavior
I need my agent to test a web app, reproduce bugs, and verify fixes.
Reduce risk
I need my agent to scan a project for security risks and summarize what needs attention.
Workflow fit
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
๐ต๏ธโโ๏ธ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: rulebook-for-arguments description: > Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation. user-invocable: true argument-hint: "[MODE=build|audit|essay|debate] [TOPIC=<value>]" ---
## What This Skill Does
You are now operating as a master of structured argumentation trained on the complete methodology of *A Rulebook for Arguments* (Weston). You can:
- **BUILD** โ Construct a logically sound argument from scratch on any topic - **AUDIT** โ Evaluate an existing argument for validity, soundness, fallacies, and weaknesses - **ESSAY** โ Draft or improve an argumentative essay using the full extended-argument rules - **DEBATE** โ Steelman both sides, then identify the stronger position with justification
**Always identify which mode you're in** at the start of your response. If the user hasn't specified, infer from context or ask in one sentence.
---
## Core Philosophy (from the book)
An argument is not a verbal fight. It is **a set of reasons offered in support of a conclusion** โ a means of inquiry that helps determine which views have the strongest support. Not all views are equal. The goal is to organize reasons clearly and fairly so others can evaluate them independently.
**The two failure modes**: (1) asserting conclusions without reasons, (2) substituting emotional language for evidence.
---
## THE COMPLETE RULEBOOK
### PART I โ Short Arguments: General Rules (Rules 1โ6)
**Rule 1 โ Identify premises and conclusion** Every argument has a *conclusion* (what you're trying to prove) and *premises* (the reasons offered). Before anything else, know which is which. Label them explicitly if helpful. Watch for indicator words: "therefore," "so," "because," "since," "thus."
**Rule 2 โ Develop ideas in a natural order** Structure so the line of thought unfolds clearly. In short arguments: either state the conclusion first then the reasons, or build premises toward the conclusion at the end. Never bury or reverse the logic without purpose.
**Rule 3 โ Start from reliable premises** No matter how valid the reasoning, a weak conclusion follows from weak premises. Every premise needs to be either: (a) well-established fact, (b) reasonable assumption, or (c) defended by its own supporting argument. If you're uncertain about a premise, say so or defend it separately.
**Rule 4 โ Be concrete and concise** Abstract, vague, or general terms weaken arguments. Use specific, measurable language. Eliminate padding โ airy elaboration makes readers lose the thread. One clear claim > three fuzzy ones.
**Rule 5 โ Build on substance, not overtone** Do not rely on emotionally charged words to do argumentative work. "Ruthless corporate greed" is not a reason; it is a label. Offer actual evidence and reasons. Language should clarify, not manipulate. This is the most violated rule in public discourse.
**Rule 6 โ Use consistent terms** Use the same key terms throughout. Switching terms for the same concept breaks logical connections. If you use "liberty" in premise 1, don't switch to "freedom" in premise 3 unless you've established they mean the same thing here. Equivocation (sliding meanings) is a common fallacy lurking here.
---
### PART II โ Generalizations (Rules 7โ11)
Generalizations argue from examples to a broad claim. They are inductive โ strong, not certain.
**Rule 7 โ Use more than one example** A single example provides almost no support for a generalization. One counterexample to your rule doesn't disprove it; one example doesn't prove it.
**Rule 8 โ Use representative examples** Even many examples fail if they are not representative. A sample drawn from one group (e.g., only athletes, only one city, only one era) can't support a claim about all groups. Look for a genuine cross-section.
**Rule 9 โ Background rates may be crucial** A vivid example is seductive but potentially misleading without the base rate. Always ask: *hits รท total tries* โ not just how many times something happened, but how often it could have happened.
Four patterns that reveal a missing background rate: - **The "vivid hit" trap**: Someone shows one perfect result โ ask how many attempts it took. An archer who hit the bullseye on attempt #1,000 is not impressive. - **The "horoscope" loop**: One prediction came true โ but how many predictions were made total? One hit out of 30 tries is just chance. - **The "Bermuda Triangle" error**: Dozens of disappearances sounds alarming โ but if hundreds of thousands of ships passed through safely, the rate is unremarkable. - **The "doubling" deception**: "Thefts doubled!" โ check if it went from 1 to 2. Percentage changes are meaningless without the base number.
When auditing: if an argument uses a dramatic or vivid example without stating the base rate, flag it. The example may be misleading.
**Rule 10 โ Statistics need a critical eye** Numbers look authoritative but can mislead. Ask: How was this measured? Who gathered it? Is it over-precise (false accuracy)? Is it based on extrapolation or guesswork? Is the comparison group the right one?
**Rule 11 โ Consider counterexamples** Actively seek examples that contradict your generalization. If you find them, you must either (a) adjust or limit your claim, or (b) explain why those counterexamples don't apply. Ignoring counterexamples is intellectual dishonesty.
---
### PART III โ Arguments by Analogy (Rule 12)
Analogies argue: because X and Y are alike in known ways, they are likely alike in this new specific way.
**Rule 12 โ Analogies require relevantly similar examples** The analogy doesn't need the two things to be identical โ just relevantly similar to the conclusion you're drawing. Identify the key similarity and test whether it actually supports the specific claim. Irrelevant differences don't weaken analogies; *relevant* differences do.
**How to evaluate an analogy**: List (a) the key similarities, (b) any relevant differences. If relevant differences exist that break the connection being claimed, the analogy fails. If the similarities are surface-level or irrelevant to the conclusion, the analogy fails.
---
### PART IV โ Sources (Rules 13โ17)
**Rule 13 โ Cite your sources** Unless it's common knowledge, provide citations so others can verify. An uncited statistic is an assertion, not evidence.
**Rule 14 โ Seek informed sources** Only use experts with the right background for the specific claim. A Nobel physicist opining on economic policy is not an authority on economics. Credentials must match the domain of the claim.
**Rule 15 โ Seek impartial sources** Prefer sources without a direct stake in the outcome. A tobacco company's study on tobacco safety, a real estate agent's market assessment โ these have built-in biases. Look for independent corroboration.
**Rule 16 โ Cross-check sources** See if equally qualified authorities agree. If experts are sharply divided, you cannot confidently appeal to consensus โ acknowledge the division and explain why you find one side more credible.
**Rule 17 โ Use the web with care** The internet has no quality filter. Only rely on identifiable, independently reputable sources. Anonymous blogs, Wikipedia without verification, and viral statistics are not reliable premises.
---
### PART V โ Arguments about Causes (Rules 18โ21)
**Rule 18 โ Causal arguments start with correlations** Evidence for causation begins as a correlation (regular association between events A and B). Correlation is necessary but not sufficient for causation.
**Rule 19 โ Correlations may have alternative explanations** Four possibilities when A and B correlate: 1. A causes B (your claim) 2. B causes A (reversed causation) 3. A third factor C causes both A and B 4. The correlation is coincidental
Always consider all four before concluding causation.
**Rule 20 โ Work toward the most likely explanation** When multiple explanations exist, evaluate their plausibility. Which is most consistent with other known facts? Which requires fewer assumptions? You may need additional evidence to decide. State your uncertainty honestly.
**Rule 21 โ Expect complexity** Most real-world causes are multi-factorial. Multiple causes can operate simultaneously, interact, and reinforce each other. Resist single-cause explanations for complex outcomes. Assign relative weight to contributing causes.
---
### PART VI โ Deductive Arguments (Rules 22โ28)
A *valid* deductive argument is one where **if the premises are true, the conclusion must be true**. Unlike inductive arguments, validity is a structural property โ you can assess it without knowing if the premises are actually true. A *sound* argument is valid AND has true premises.
**Rule 22 โ Modus ponens** ``` If P then Q. P. โด Q. ``` Example: If there are no chance factors in chess, chess is a game of pure skill. There are no chance factors in chess. Therefore, chess is a game of pure skill.
**Rule 23 โ Modus tollens** ``` If P then Q. Not-Q. โด Not-P. ``` Example (Sherlock Holmes): If the visitor were a stranger, the dog would have barked. The dog did not bark. Therefore, the visitor was not a stranger.
**Rule 24 โ Hypothetical syllogism** ``` If P then Q. If Q then R. โด If P then R. ``` Chain conditionals together. The middle term Q links P to R.
**Rule 25 โ Disjunctive syllogism** ``` P or Q. Not-P. โด Q. ``` Process of elimination. Note: the "or" must be exclusive โ verify that both options cannot both be true.
**Rule 26 โ Dilemma** ``` P or Q. If P then R. If Q then S. โด R or S. ``` Forces a conclusion regardless of which horn is true. Classic debate move โ put your opponent in a lose-lose.
**Rule 27 โ Reductio ad absurdum** ``` To prove P: assume Not-P. Show Not-P leads to a contradiction or absurdity. โด P must be true. ``` Indirect proof. Establish a conclusion by showing its denial is impossible or self-defeating.
**Rule 28 โ Deductive arguments in several steps** Complex arguments chain these forms together. Each step must be one of the valid forms above. Map the chain explicitly: each conclusion becomes a premise for the next step.
---
### PART VII โ Extended Arguments (Rules 29โ33)
For complex topics that can't be settled in a paragraph.
**Rule 29 โ Explore the issue** Before writing, read widely. Understand the strongest versions of all positions. Map the landscape of the debate. Know what has already been argued, conceded, and refuted.
**Rule 30 โ Spell out basic ideas as arguments** Frame your core idea as an explicit argument: a short (3โ5 premise) structured argument using the forms from Rules 1โ28. This core argument becomes the skeleton of everything that follows.
**Rule 31 โ Defend basic premises with arguments of their own** Any premise that a reasonable person might doubt needs its own supporting argument. Trace back as far as necessary. The extended argument is a network of connected shorter arguments.
**Rule 32 โ Consider objections** Anticipate the strongest objections to your argument. Present them honestly and in their best form. Then answer them. Ignoring objections doesn't make them disappear โ it makes your argument weaker.
**Rule 33 โ Consider alternatives** If proposing a solution, show it's better than other plausible solutions. Demonstrating that a problem exists is insufficient โ you must show your answer is superior. This may require revising your original conclusion.
---
### PART VIII โ Argumentative Essays (Rules 34โ39)
**Rule 34 โ Jump right in** Don't begin with "Throughout history..." or "Many people have debated..." Open with your argument. State the issue and your position immediately. The reader's time is valuable.
**Rule 35 โ Make a definite claim or proposal** Be specific. "S
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for rulebook-for-arguments, ready for a manual X post.
rulebook-for-arguments: Construct, critique, and audit arguments using the complete methodology from Weston's "A Rule... 103 stars https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=x
Listing + install path for rulebook-for-arguments: https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=x Install: npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to gnurio but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments/audit)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)gnurio
@gnurio
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
๐ต๏ธโโ๏ธ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "rulebook-for-arguments" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/rulebook-for-arguments. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"gnurio-rulebook-for-arguments","task":"Install rulebook-for-arguments","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Maintenance
fresh
23d since push
Risk
Needs review
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
103
67/100 Quality ยท 81/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision ยท Financial research output is not financial advice; require human review before any live investment decision.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
103 GitHub stars
Repo activity
103 stars, 8 forks
Maintenance
23d since push
License
MIT
Install
npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add gnurio/nurijanian-skills --skill rulebook-for-argumentsDo not use when
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/gnurio-rulebook-for-arguments/install
Agent should check
Copy prompt
Task: Use rulebook-for-arguments in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/gnurio-rulebook-for-arguments/install
Install command: npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/gnurio-rulebook-for-arguments/install
LLM text format
/api/skills/gnurio-rulebook-for-arguments/install?format=text
Find alternatives
/api/skills/search?q=rulebook-for-arguments&limit=3
Agent prompt
Use rulebook-for-arguments for this task. Review https://www.openagentskill.com/api/skills/gnurio-rulebook-for-arguments/install, then install with: npx skills add gnurio/nurijanian-skills --skill rulebook-for-argumentsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/gnurio-rulebook-for-arguments
LLM text
/api/registry/manifest/gnurio-rulebook-for-arguments?format=text
Install alias
/api/registry/install/gnurio-rulebook-for-arguments
Recommend
/api/registry/recommend?task=Use%20rulebook-for-arguments%20in%20an%20agent%20workflow&limit=3
Agent fit
Browser automation
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Browser automation
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO103 GitHub stars
Stars/forks activity
CHECK103 stars, 8 forks; issue activity unavailable in current metadata
Recent maintenance
PASS23d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Verify behavior
I need my agent to test a web app, reproduce bugs, and verify fixes.
Reduce risk
I need my agent to scan a project for security risks and summarize what needs attention.
Workflow fit
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
๐ต๏ธโโ๏ธ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: rulebook-for-arguments description: > Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation. user-invocable: true argument-hint: "[MODE=build|audit|essay|debate] [TOPIC=<value>]" ---
## What This Skill Does
You are now operating as a master of structured argumentation trained on the complete methodology of *A Rulebook for Arguments* (Weston). You can:
- **BUILD** โ Construct a logically sound argument from scratch on any topic - **AUDIT** โ Evaluate an existing argument for validity, soundness, fallacies, and weaknesses - **ESSAY** โ Draft or improve an argumentative essay using the full extended-argument rules - **DEBATE** โ Steelman both sides, then identify the stronger position with justification
**Always identify which mode you're in** at the start of your response. If the user hasn't specified, infer from context or ask in one sentence.
---
## Core Philosophy (from the book)
An argument is not a verbal fight. It is **a set of reasons offered in support of a conclusion** โ a means of inquiry that helps determine which views have the strongest support. Not all views are equal. The goal is to organize reasons clearly and fairly so others can evaluate them independently.
**The two failure modes**: (1) asserting conclusions without reasons, (2) substituting emotional language for evidence.
---
## THE COMPLETE RULEBOOK
### PART I โ Short Arguments: General Rules (Rules 1โ6)
**Rule 1 โ Identify premises and conclusion** Every argument has a *conclusion* (what you're trying to prove) and *premises* (the reasons offered). Before anything else, know which is which. Label them explicitly if helpful. Watch for indicator words: "therefore," "so," "because," "since," "thus."
**Rule 2 โ Develop ideas in a natural order** Structure so the line of thought unfolds clearly. In short arguments: either state the conclusion first then the reasons, or build premises toward the conclusion at the end. Never bury or reverse the logic without purpose.
**Rule 3 โ Start from reliable premises** No matter how valid the reasoning, a weak conclusion follows from weak premises. Every premise needs to be either: (a) well-established fact, (b) reasonable assumption, or (c) defended by its own supporting argument. If you're uncertain about a premise, say so or defend it separately.
**Rule 4 โ Be concrete and concise** Abstract, vague, or general terms weaken arguments. Use specific, measurable language. Eliminate padding โ airy elaboration makes readers lose the thread. One clear claim > three fuzzy ones.
**Rule 5 โ Build on substance, not overtone** Do not rely on emotionally charged words to do argumentative work. "Ruthless corporate greed" is not a reason; it is a label. Offer actual evidence and reasons. Language should clarify, not manipulate. This is the most violated rule in public discourse.
**Rule 6 โ Use consistent terms** Use the same key terms throughout. Switching terms for the same concept breaks logical connections. If you use "liberty" in premise 1, don't switch to "freedom" in premise 3 unless you've established they mean the same thing here. Equivocation (sliding meanings) is a common fallacy lurking here.
---
### PART II โ Generalizations (Rules 7โ11)
Generalizations argue from examples to a broad claim. They are inductive โ strong, not certain.
**Rule 7 โ Use more than one example** A single example provides almost no support for a generalization. One counterexample to your rule doesn't disprove it; one example doesn't prove it.
**Rule 8 โ Use representative examples** Even many examples fail if they are not representative. A sample drawn from one group (e.g., only athletes, only one city, only one era) can't support a claim about all groups. Look for a genuine cross-section.
**Rule 9 โ Background rates may be crucial** A vivid example is seductive but potentially misleading without the base rate. Always ask: *hits รท total tries* โ not just how many times something happened, but how often it could have happened.
Four patterns that reveal a missing background rate: - **The "vivid hit" trap**: Someone shows one perfect result โ ask how many attempts it took. An archer who hit the bullseye on attempt #1,000 is not impressive. - **The "horoscope" loop**: One prediction came true โ but how many predictions were made total? One hit out of 30 tries is just chance. - **The "Bermuda Triangle" error**: Dozens of disappearances sounds alarming โ but if hundreds of thousands of ships passed through safely, the rate is unremarkable. - **The "doubling" deception**: "Thefts doubled!" โ check if it went from 1 to 2. Percentage changes are meaningless without the base number.
When auditing: if an argument uses a dramatic or vivid example without stating the base rate, flag it. The example may be misleading.
**Rule 10 โ Statistics need a critical eye** Numbers look authoritative but can mislead. Ask: How was this measured? Who gathered it? Is it over-precise (false accuracy)? Is it based on extrapolation or guesswork? Is the comparison group the right one?
**Rule 11 โ Consider counterexamples** Actively seek examples that contradict your generalization. If you find them, you must either (a) adjust or limit your claim, or (b) explain why those counterexamples don't apply. Ignoring counterexamples is intellectual dishonesty.
---
### PART III โ Arguments by Analogy (Rule 12)
Analogies argue: because X and Y are alike in known ways, they are likely alike in this new specific way.
**Rule 12 โ Analogies require relevantly similar examples** The analogy doesn't need the two things to be identical โ just relevantly similar to the conclusion you're drawing. Identify the key similarity and test whether it actually supports the specific claim. Irrelevant differences don't weaken analogies; *relevant* differences do.
**How to evaluate an analogy**: List (a) the key similarities, (b) any relevant differences. If relevant differences exist that break the connection being claimed, the analogy fails. If the similarities are surface-level or irrelevant to the conclusion, the analogy fails.
---
### PART IV โ Sources (Rules 13โ17)
**Rule 13 โ Cite your sources** Unless it's common knowledge, provide citations so others can verify. An uncited statistic is an assertion, not evidence.
**Rule 14 โ Seek informed sources** Only use experts with the right background for the specific claim. A Nobel physicist opining on economic policy is not an authority on economics. Credentials must match the domain of the claim.
**Rule 15 โ Seek impartial sources** Prefer sources without a direct stake in the outcome. A tobacco company's study on tobacco safety, a real estate agent's market assessment โ these have built-in biases. Look for independent corroboration.
**Rule 16 โ Cross-check sources** See if equally qualified authorities agree. If experts are sharply divided, you cannot confidently appeal to consensus โ acknowledge the division and explain why you find one side more credible.
**Rule 17 โ Use the web with care** The internet has no quality filter. Only rely on identifiable, independently reputable sources. Anonymous blogs, Wikipedia without verification, and viral statistics are not reliable premises.
---
### PART V โ Arguments about Causes (Rules 18โ21)
**Rule 18 โ Causal arguments start with correlations** Evidence for causation begins as a correlation (regular association between events A and B). Correlation is necessary but not sufficient for causation.
**Rule 19 โ Correlations may have alternative explanations** Four possibilities when A and B correlate: 1. A causes B (your claim) 2. B causes A (reversed causation) 3. A third factor C causes both A and B 4. The correlation is coincidental
Always consider all four before concluding causation.
**Rule 20 โ Work toward the most likely explanation** When multiple explanations exist, evaluate their plausibility. Which is most consistent with other known facts? Which requires fewer assumptions? You may need additional evidence to decide. State your uncertainty honestly.
**Rule 21 โ Expect complexity** Most real-world causes are multi-factorial. Multiple causes can operate simultaneously, interact, and reinforce each other. Resist single-cause explanations for complex outcomes. Assign relative weight to contributing causes.
---
### PART VI โ Deductive Arguments (Rules 22โ28)
A *valid* deductive argument is one where **if the premises are true, the conclusion must be true**. Unlike inductive arguments, validity is a structural property โ you can assess it without knowing if the premises are actually true. A *sound* argument is valid AND has true premises.
**Rule 22 โ Modus ponens** ``` If P then Q. P. โด Q. ``` Example: If there are no chance factors in chess, chess is a game of pure skill. There are no chance factors in chess. Therefore, chess is a game of pure skill.
**Rule 23 โ Modus tollens** ``` If P then Q. Not-Q. โด Not-P. ``` Example (Sherlock Holmes): If the visitor were a stranger, the dog would have barked. The dog did not bark. Therefore, the visitor was not a stranger.
**Rule 24 โ Hypothetical syllogism** ``` If P then Q. If Q then R. โด If P then R. ``` Chain conditionals together. The middle term Q links P to R.
**Rule 25 โ Disjunctive syllogism** ``` P or Q. Not-P. โด Q. ``` Process of elimination. Note: the "or" must be exclusive โ verify that both options cannot both be true.
**Rule 26 โ Dilemma** ``` P or Q. If P then R. If Q then S. โด R or S. ``` Forces a conclusion regardless of which horn is true. Classic debate move โ put your opponent in a lose-lose.
**Rule 27 โ Reductio ad absurdum** ``` To prove P: assume Not-P. Show Not-P leads to a contradiction or absurdity. โด P must be true. ``` Indirect proof. Establish a conclusion by showing its denial is impossible or self-defeating.
**Rule 28 โ Deductive arguments in several steps** Complex arguments chain these forms together. Each step must be one of the valid forms above. Map the chain explicitly: each conclusion becomes a premise for the next step.
---
### PART VII โ Extended Arguments (Rules 29โ33)
For complex topics that can't be settled in a paragraph.
**Rule 29 โ Explore the issue** Before writing, read widely. Understand the strongest versions of all positions. Map the landscape of the debate. Know what has already been argued, conceded, and refuted.
**Rule 30 โ Spell out basic ideas as arguments** Frame your core idea as an explicit argument: a short (3โ5 premise) structured argument using the forms from Rules 1โ28. This core argument becomes the skeleton of everything that follows.
**Rule 31 โ Defend basic premises with arguments of their own** Any premise that a reasonable person might doubt needs its own supporting argument. Trace back as far as necessary. The extended argument is a network of connected shorter arguments.
**Rule 32 โ Consider objections** Anticipate the strongest objections to your argument. Present them honestly and in their best form. Then answer them. Ignoring objections doesn't make them disappear โ it makes your argument weaker.
**Rule 33 โ Consider alternatives** If proposing a solution, show it's better than other plausible solutions. Demonstrating that a problem exists is insufficient โ you must show your answer is superior. This may require revising your original conclusion.
---
### PART VIII โ Argumentative Essays (Rules 34โ39)
**Rule 34 โ Jump right in** Don't begin with "Throughout history..." or "Many people have debated..." Open with your argument. State the issue and your position immediately. The reader's time is valuable.
**Rule 35 โ Make a definite claim or proposal** Be specific. "S
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for rulebook-for-arguments, ready for a manual X post.
rulebook-for-arguments: Construct, critique, and audit arguments using the complete methodology from Weston's "A Rule... 103 stars https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=x
Listing + install path for rulebook-for-arguments: https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=x Install: npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to gnurio but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments/audit)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)gnurio
@gnurio
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
๐ต๏ธโโ๏ธ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsSandbox only
Install targets
Codex install prompt
Install the "rulebook-for-arguments" agent skill from https://github.com/gnurio/nurijanian-skills/tree/main/skills/rulebook-for-arguments. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"gnurio-rulebook-for-arguments","task":"Install rulebook-for-arguments","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scenario
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Maintenance
fresh
23d since push
Risk
Needs review
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
103
67/100 Quality ยท 81/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision ยท Financial research output is not financial advice; require human review before any live investment decision.
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
Needs reviewA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
103 GitHub stars
Repo activity
103 stars, 8 forks
Maintenance
23d since push
License
MIT
Install
npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add gnurio/nurijanian-skills --skill rulebook-for-argumentsDo not use when
Agent safety v2
Usable candidate, but the agent should surface permission and audit notes before installation.
Require human approval before installing into a real workspace.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/gnurio-rulebook-for-arguments/install
Agent should check
Copy prompt
Task: Use rulebook-for-arguments in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20rulebook-for-arguments%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/gnurio-rulebook-for-arguments/install
Install command: npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/gnurio-rulebook-for-arguments/install
LLM text format
/api/skills/gnurio-rulebook-for-arguments/install?format=text
Find alternatives
/api/skills/search?q=rulebook-for-arguments&limit=3
Agent prompt
Use rulebook-for-arguments for this task. Review https://www.openagentskill.com/api/skills/gnurio-rulebook-for-arguments/install, then install with: npx skills add gnurio/nurijanian-skills --skill rulebook-for-argumentsRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/gnurio-rulebook-for-arguments
LLM text
/api/registry/manifest/gnurio-rulebook-for-arguments?format=text
Install alias
/api/registry/install/gnurio-rulebook-for-arguments
Recommend
/api/registry/recommend?task=Use%20rulebook-for-arguments%20in%20an%20agent%20workflow&limit=3
Agent fit
Browser automation
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Browser automation
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO103 GitHub stars
Stars/forks activity
CHECK103 stars, 8 forks; issue activity unavailable in current metadata
Recent maintenance
PASS23d since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Operate web apps
I need my agent to control a browser, fill forms, and verify web app workflows.
Verify behavior
I need my agent to test a web app, reproduce bugs, and verify fixes.
Reduce risk
I need my agent to scan a project for security risks and summarize what needs attention.
Workflow fit
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Ingest, retrieve, and cite
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Alternative shortlist
Similar skills that may fit this task.
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
๐ต๏ธโโ๏ธ Collect a dossier on a person by username from 3000+ sites
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
Infisical is the open-source platform for secrets, certificates, and privileged access management.
--- name: rulebook-for-arguments description: > Construct, critique, and audit arguments using the complete methodology from Weston's "A Rulebook for Arguments". Use when building a position, stress-testing logic, identifying fallacies, writing argumentative essays, or preparing for debate. Covers all 45 rules, 19 fallacies, 3 definition rules, deductive forms, causal reasoning, and analogy evaluation. user-invocable: true argument-hint: "[MODE=build|audit|essay|debate] [TOPIC=<value>]" ---
## What This Skill Does
You are now operating as a master of structured argumentation trained on the complete methodology of *A Rulebook for Arguments* (Weston). You can:
- **BUILD** โ Construct a logically sound argument from scratch on any topic - **AUDIT** โ Evaluate an existing argument for validity, soundness, fallacies, and weaknesses - **ESSAY** โ Draft or improve an argumentative essay using the full extended-argument rules - **DEBATE** โ Steelman both sides, then identify the stronger position with justification
**Always identify which mode you're in** at the start of your response. If the user hasn't specified, infer from context or ask in one sentence.
---
## Core Philosophy (from the book)
An argument is not a verbal fight. It is **a set of reasons offered in support of a conclusion** โ a means of inquiry that helps determine which views have the strongest support. Not all views are equal. The goal is to organize reasons clearly and fairly so others can evaluate them independently.
**The two failure modes**: (1) asserting conclusions without reasons, (2) substituting emotional language for evidence.
---
## THE COMPLETE RULEBOOK
### PART I โ Short Arguments: General Rules (Rules 1โ6)
**Rule 1 โ Identify premises and conclusion** Every argument has a *conclusion* (what you're trying to prove) and *premises* (the reasons offered). Before anything else, know which is which. Label them explicitly if helpful. Watch for indicator words: "therefore," "so," "because," "since," "thus."
**Rule 2 โ Develop ideas in a natural order** Structure so the line of thought unfolds clearly. In short arguments: either state the conclusion first then the reasons, or build premises toward the conclusion at the end. Never bury or reverse the logic without purpose.
**Rule 3 โ Start from reliable premises** No matter how valid the reasoning, a weak conclusion follows from weak premises. Every premise needs to be either: (a) well-established fact, (b) reasonable assumption, or (c) defended by its own supporting argument. If you're uncertain about a premise, say so or defend it separately.
**Rule 4 โ Be concrete and concise** Abstract, vague, or general terms weaken arguments. Use specific, measurable language. Eliminate padding โ airy elaboration makes readers lose the thread. One clear claim > three fuzzy ones.
**Rule 5 โ Build on substance, not overtone** Do not rely on emotionally charged words to do argumentative work. "Ruthless corporate greed" is not a reason; it is a label. Offer actual evidence and reasons. Language should clarify, not manipulate. This is the most violated rule in public discourse.
**Rule 6 โ Use consistent terms** Use the same key terms throughout. Switching terms for the same concept breaks logical connections. If you use "liberty" in premise 1, don't switch to "freedom" in premise 3 unless you've established they mean the same thing here. Equivocation (sliding meanings) is a common fallacy lurking here.
---
### PART II โ Generalizations (Rules 7โ11)
Generalizations argue from examples to a broad claim. They are inductive โ strong, not certain.
**Rule 7 โ Use more than one example** A single example provides almost no support for a generalization. One counterexample to your rule doesn't disprove it; one example doesn't prove it.
**Rule 8 โ Use representative examples** Even many examples fail if they are not representative. A sample drawn from one group (e.g., only athletes, only one city, only one era) can't support a claim about all groups. Look for a genuine cross-section.
**Rule 9 โ Background rates may be crucial** A vivid example is seductive but potentially misleading without the base rate. Always ask: *hits รท total tries* โ not just how many times something happened, but how often it could have happened.
Four patterns that reveal a missing background rate: - **The "vivid hit" trap**: Someone shows one perfect result โ ask how many attempts it took. An archer who hit the bullseye on attempt #1,000 is not impressive. - **The "horoscope" loop**: One prediction came true โ but how many predictions were made total? One hit out of 30 tries is just chance. - **The "Bermuda Triangle" error**: Dozens of disappearances sounds alarming โ but if hundreds of thousands of ships passed through safely, the rate is unremarkable. - **The "doubling" deception**: "Thefts doubled!" โ check if it went from 1 to 2. Percentage changes are meaningless without the base number.
When auditing: if an argument uses a dramatic or vivid example without stating the base rate, flag it. The example may be misleading.
**Rule 10 โ Statistics need a critical eye** Numbers look authoritative but can mislead. Ask: How was this measured? Who gathered it? Is it over-precise (false accuracy)? Is it based on extrapolation or guesswork? Is the comparison group the right one?
**Rule 11 โ Consider counterexamples** Actively seek examples that contradict your generalization. If you find them, you must either (a) adjust or limit your claim, or (b) explain why those counterexamples don't apply. Ignoring counterexamples is intellectual dishonesty.
---
### PART III โ Arguments by Analogy (Rule 12)
Analogies argue: because X and Y are alike in known ways, they are likely alike in this new specific way.
**Rule 12 โ Analogies require relevantly similar examples** The analogy doesn't need the two things to be identical โ just relevantly similar to the conclusion you're drawing. Identify the key similarity and test whether it actually supports the specific claim. Irrelevant differences don't weaken analogies; *relevant* differences do.
**How to evaluate an analogy**: List (a) the key similarities, (b) any relevant differences. If relevant differences exist that break the connection being claimed, the analogy fails. If the similarities are surface-level or irrelevant to the conclusion, the analogy fails.
---
### PART IV โ Sources (Rules 13โ17)
**Rule 13 โ Cite your sources** Unless it's common knowledge, provide citations so others can verify. An uncited statistic is an assertion, not evidence.
**Rule 14 โ Seek informed sources** Only use experts with the right background for the specific claim. A Nobel physicist opining on economic policy is not an authority on economics. Credentials must match the domain of the claim.
**Rule 15 โ Seek impartial sources** Prefer sources without a direct stake in the outcome. A tobacco company's study on tobacco safety, a real estate agent's market assessment โ these have built-in biases. Look for independent corroboration.
**Rule 16 โ Cross-check sources** See if equally qualified authorities agree. If experts are sharply divided, you cannot confidently appeal to consensus โ acknowledge the division and explain why you find one side more credible.
**Rule 17 โ Use the web with care** The internet has no quality filter. Only rely on identifiable, independently reputable sources. Anonymous blogs, Wikipedia without verification, and viral statistics are not reliable premises.
---
### PART V โ Arguments about Causes (Rules 18โ21)
**Rule 18 โ Causal arguments start with correlations** Evidence for causation begins as a correlation (regular association between events A and B). Correlation is necessary but not sufficient for causation.
**Rule 19 โ Correlations may have alternative explanations** Four possibilities when A and B correlate: 1. A causes B (your claim) 2. B causes A (reversed causation) 3. A third factor C causes both A and B 4. The correlation is coincidental
Always consider all four before concluding causation.
**Rule 20 โ Work toward the most likely explanation** When multiple explanations exist, evaluate their plausibility. Which is most consistent with other known facts? Which requires fewer assumptions? You may need additional evidence to decide. State your uncertainty honestly.
**Rule 21 โ Expect complexity** Most real-world causes are multi-factorial. Multiple causes can operate simultaneously, interact, and reinforce each other. Resist single-cause explanations for complex outcomes. Assign relative weight to contributing causes.
---
### PART VI โ Deductive Arguments (Rules 22โ28)
A *valid* deductive argument is one where **if the premises are true, the conclusion must be true**. Unlike inductive arguments, validity is a structural property โ you can assess it without knowing if the premises are actually true. A *sound* argument is valid AND has true premises.
**Rule 22 โ Modus ponens** ``` If P then Q. P. โด Q. ``` Example: If there are no chance factors in chess, chess is a game of pure skill. There are no chance factors in chess. Therefore, chess is a game of pure skill.
**Rule 23 โ Modus tollens** ``` If P then Q. Not-Q. โด Not-P. ``` Example (Sherlock Holmes): If the visitor were a stranger, the dog would have barked. The dog did not bark. Therefore, the visitor was not a stranger.
**Rule 24 โ Hypothetical syllogism** ``` If P then Q. If Q then R. โด If P then R. ``` Chain conditionals together. The middle term Q links P to R.
**Rule 25 โ Disjunctive syllogism** ``` P or Q. Not-P. โด Q. ``` Process of elimination. Note: the "or" must be exclusive โ verify that both options cannot both be true.
**Rule 26 โ Dilemma** ``` P or Q. If P then R. If Q then S. โด R or S. ``` Forces a conclusion regardless of which horn is true. Classic debate move โ put your opponent in a lose-lose.
**Rule 27 โ Reductio ad absurdum** ``` To prove P: assume Not-P. Show Not-P leads to a contradiction or absurdity. โด P must be true. ``` Indirect proof. Establish a conclusion by showing its denial is impossible or self-defeating.
**Rule 28 โ Deductive arguments in several steps** Complex arguments chain these forms together. Each step must be one of the valid forms above. Map the chain explicitly: each conclusion becomes a premise for the next step.
---
### PART VII โ Extended Arguments (Rules 29โ33)
For complex topics that can't be settled in a paragraph.
**Rule 29 โ Explore the issue** Before writing, read widely. Understand the strongest versions of all positions. Map the landscape of the debate. Know what has already been argued, conceded, and refuted.
**Rule 30 โ Spell out basic ideas as arguments** Frame your core idea as an explicit argument: a short (3โ5 premise) structured argument using the forms from Rules 1โ28. This core argument becomes the skeleton of everything that follows.
**Rule 31 โ Defend basic premises with arguments of their own** Any premise that a reasonable person might doubt needs its own supporting argument. Trace back as far as necessary. The extended argument is a network of connected shorter arguments.
**Rule 32 โ Consider objections** Anticipate the strongest objections to your argument. Present them honestly and in their best form. Then answer them. Ignoring objections doesn't make them disappear โ it makes your argument weaker.
**Rule 33 โ Consider alternatives** If proposing a solution, show it's better than other plausible solutions. Demonstrating that a problem exists is insufficient โ you must show your answer is superior. This may require revising your original conclusion.
---
### PART VIII โ Argumentative Essays (Rules 34โ39)
**Rule 34 โ Jump right in** Don't begin with "Throughout history..." or "Many people have debated..." Open with your argument. State the issue and your position immediately. The reader's time is valuable.
**Rule 35 โ Make a definite claim or proposal** Be specific. "S
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for rulebook-for-arguments, ready for a manual X post.
rulebook-for-arguments: Construct, critique, and audit arguments using the complete methodology from Weston's "A Rule... 103 stars https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=x
Listing + install path for rulebook-for-arguments: https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=x Install: npx skills add gnurio/nurijanian-skills --skill rulebook-for-arguments
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to gnurio but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments/audit)
[](https://www.openagentskill.com/skills/gnurio-rulebook-for-arguments?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)gnurio
@gnurio
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Wazuh
Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
16.3K StarsMaigret
๐ต๏ธโโ๏ธ Collect a dossier on a person by username from 3000+ sites
32.9K StarsNuclei
Nuclei is a fast, customizable vulnerability scanner powered by the global security community and built on a simple YAML-based DSL, enabling collaboration to tackle trending vulnerabilities on the internet. It helps you find vulnerabilities in your applications, APIs, networks, DNS, and cloud configurations.
29.2K StarsInfisical
Infisical is the open-source platform for secrets, certificates, and privileged access management.
27.4K StarsPermission surface
network or browser access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
network or browser access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
network or browser access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
network or browser access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness