anti-defensive-writing

REVIEW · 73
Registry indexed

Reduce defensive writing in drafts and revisions by removing unnecessary caveats, disclaimers, hedges, apology-like framing, negative self-limiting statements, and over-explanations while preserving necessary scope, accuracy, safety, legal, ethical, and methodological limits. Use

Verified installs0
Stars136
Version1.0.0
Quality68/100 · Promising
Trust73/100 · Sandbox only
Audit83/100 · Safe to try

Supply asset profile

Research and knowledge work

Deep research, source comparison, literature review, RAG, knowledge search, and reports.

Browse track

Scenario

Research agents

I need my agent to research a topic, compare sources, and produce a concise report.

Agent fit

Claude Code + CLI + Codex

Codex, Claude Code, Cursor, CLI, or custom agents.

Install

Ready

npx skills add Kiterlin/anti-defensive-writing --skill anti-defensive-writing

Maintenance

fresh

Pushed today

Risk

Safe to try

Quality score needs review

GitHub quality

136

68/100 Quality · 81/100 Trust

Coverage tags

ResearchResearch agentsautomationagent-skill

Review notes

Quality score needs review · Stars/forks activity: 136 stars, 3 forks; issue activity unavailable in current metadata

Agent adoption scorecard

Trust, audit, and install readiness at a glance

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

Promising
68

Useful candidate, but compare it with alternatives before adopting.

Trust

Sandbox only
73

Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.

Audit

Safe to try
83

A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.

OpenAgentSkill Trust Score v5

Human review before install

Run only in a sandbox and compare close alternatives before using it for real work.

CodexClaude CodeCursorOpenAgentSkill CLI

Stars

136 GitHub stars

Repo activity

136 stars, 3 forks

Maintenance

Pushed today

License

MIT

Install

npx skills add Kiterlin/anti-defensive-writing --skill anti-defensive-writing

Install safety

standard package or runtime install path

Permission surface

no high-risk permission surface in public metadata

Agent outcomes

No agent outcome data yet

Docs

Strong README/SKILL.md context

Risk summary

Review before production

  • Quality score needs review
  • Stars/forks activity: 136 stars, 3 forks; issue activity unavailable in current metadata

Install readiness

Install path available

  • Install path is available
  • Repository evidence is available
  • License is declared
  • No Agent Proven outcome evidence yet

Agent-readable metadata

Machine-readable decision data for this skill.

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.

Open JSON

Suited tasks

  • Research agents workflows
  • Claude Code teams
  • builders willing to evaluate younger projects
  • Search sources

Suited agents

CodexClaude CodeCursorOpenAgentSkill CLICLI

Install decision

Command
npx skills add Kiterlin/anti-defensive-writing --skill anti-defensive-writing
Policy
review
Human review
yes

Trust and risk

Trust
73/100
Audit
83/100
Risk level
Safe to try

Outcome loop

Endpoint
/api/agent/outcome
Event ID
resolve
Outcomes
5

Install command

npx skills add Kiterlin/anti-defensive-writing --skill anti-defensive-writing

Do not use when

  • teams that need a vendor-supported SLA
  • high-compliance environments without internal security review
  • No OpenAgentSkill engagement data yet
  • Quality score needs review
  • Stars/forks activity: 136 stars, 3 forks; issue activity unavailable in current metadata

Agent safety v2

71/100 · Review before install

Reviewedreview

Good audit and safety signals with no high-risk permission hints in public metadata.

Review the audit page, then allow agent install in a sandboxed workflow.

Resolve via API

medium

Network access

Skill likely fetches remote pages, APIs, repositories, or external services.

  • Quality score needs review

Install targets

Install this skill in your agent workflow

Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.

skill install

OpenAgentSkill CLI

Resolve policy, run the source installer safely, and report a verified install receipt.

$ npx --yes https://github.com/Leon-Drq/openagentskill/releases/download/cli-v0.2.1/openagentskill-0.2.1.tgz install kiterlin-anti-defensive-writing

Agent resolve plan

Let an agent verify fit before installing.

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 text plan

Agent should check

  • Task fit and alternatives from Resolve API.
  • Audit score, trust score, and safety policy warnings.
  • Install target compatibility for Codex, Claude Code, Cursor, or CLI.

Copy prompt

Task: Use anti-defensive-writing in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20anti-defensive-writing%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/kiterlin-anti-defensive-writing/install
Install command: npx skills add Kiterlin/anti-defensive-writing --skill anti-defensive-writing
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.

Agent handoff

Give an agent the install path, not another directory page.

Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.

Open install API

Agent prompt

Use anti-defensive-writing for this task. Review https://www.openagentskill.com/api/skills/kiterlin-anti-defensive-writing/install, then install with: npx skills add Kiterlin/anti-defensive-writing --skill anti-defensive-writing

Registry metadata

Agent-readable profile for automatic skill selection.

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.

Open manifest

Agent fit

67/100

Research agents

Platforms

Claude Code

Audit report

Safe to try · 83/100

A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.

View audit reportView eval report

Agent decision cockpit

Fallback candidate for Research agents

Prototype with this skill first; keep a fallback candidate ready.

67
Readiness
Prototype
Stage

Role in stack

Fallback candidate

Primary fit

Research agents

Trust label

Prototype first

Install path

Command ready

Use when

  • Research agents workflows
  • Claude Code teams
  • builders willing to evaluate younger projects

Evidence

  • recent repository activity
  • install command or GitHub repo available
  • 68/100 quality profile

review first

  • No OpenAgentSkill engagement data yet

Implementation path

  1. 1Install it in a sandbox agent and run one Research agents task end to end.
  2. 2Compare output quality, latency, and failure behavior against at least one alternative.
  3. 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.

Trust profile

Sandbox only

Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.

73
OpenAgentSkill Trust Score

GitHub adoption

INFO

136 GitHub stars

Stars/forks activity

CHECK

136 stars, 3 forks; issue activity unavailable in current metadata

Recent maintenance

PASS

Pushed today

License clarity

PASS

MIT

Good signals

  • AI review approved
  • Install path is available
  • Repository evidence is available
  • Recently maintained repository
  • Install command has no obvious high-risk pattern
  • Outcome loop is ready but needs first real agent run

Review before install

  • Quality score needs review
  • Stars/forks activity: 136 stars, 3 forks; issue activity unavailable in current metadata
  • No real agent outcome reports yet
  • Human review required before unattended installation

Recommended action

Run only in a sandbox and compare close alternatives before using it for real work.

Quality profile

Promising candidate for agent workflows

Useful candidate, but compare it with alternatives before adopting.

68
GitHub stars
136
Freshness
Today
Install ready
Yes
License
MIT

Workflow fit

Use this skill in these scenarios

Workflow fit

Add it to a complete workflow

Alternative shortlist

Compare before you install

Similar skills that may fit this task.

Compare all

Overview

--- name: anti-defensive-writing description: Reduce defensive writing in drafts and revisions by removing unnecessary caveats, disclaimers, hedges, apology-like framing, negative self-limiting statements, and over-explanations while preserving necessary scope, accuracy, safety, legal, ethical, and methodological limits. Use when drafting or revising academic writing, papers, essays, abstracts, introductions, contribution statements, discussions, conclusions, technical explanations, grant writing, product writing, policy writing, professional reports, or any text the user wants to be clearer, stronger, more direct, more concise, more confident, less verbose, less caveated, less apologetic, or less defensive. ---

# Anti-Defensive Writing

## Core Rule

Advance the claim directly.

Say what is true, what the text argues, what the evidence shows, or what the method does. Do not default to explaining what the text does not claim, does not prove, does not imply, does not cover, or does not attempt.

Use a calm, competent authorial posture. Write as an author explaining an argument to the reader, not as an author negotiating with an imagined critic.

## Preserve Necessary Precision

Keep limitations when they are necessary for accuracy, ethics, law, safety, or methodological transparency.

A limitation is necessary when it affects:

- the validity of the claim; - the interpretation of the evidence; - the scope of application; - the research design; - the reader's ability to use the result correctly.

Write necessary limitations once, clearly and calmly. Place them in the appropriate section, usually methods, discussion, or limitations. Do not scatter them through abstracts, introductions, contribution paragraphs, topic sentences, conclusions, or executive summaries unless the limitation is essential to that exact sentence.

## Detection Checklist

Before finalizing a draft or revision, check for:

- unnecessary disclaimers; - repeated statements of what the text does not claim; - excessive hedging; - caveats in high-impact positions; - paragraphs that start with limitations; - negative framing where positive framing would work; - explanations added only to prevent hypothetical misunderstanding; - self-undermining contribution statements; - unnecessary "not X but Y" structures; - redundant "however", "nevertheless", or "although" transitions.

Revise any item that weakens the text without improving accuracy.

## Rewrite Procedure

1. Identify the function of the defensive sentence.

Classify it as one of:

- unnecessary disclaimer; - necessary scope condition; - real methodological limitation; - useful conceptual contrast; - evidence-based qualification; - redundant clarification.

2. Delete unnecessary disclaimers.

Remove any sentence that does not add evidence, scope, logic, conceptual precision, or necessary reader guidance.

3. Convert defensive limitation into positive scope.

Prefer:

> The analysis focuses on urban governance cases from 2015 to 2023.

Avoid:

> We do not claim that these cases are representative of all urban governance contexts.

4. Replace hedging with precision.

Prefer:

> The evidence indicates that X influences Y in these cases.

Avoid:

> This may suggest that X could potentially influence Y.

If uncertainty is real, specify its source:

> The available evidence supports this interpretation, although the design does not estimate population-level effects.

5. Rebuild the paragraph around the main point.

Ensure the paragraph has:

- a clear topic sentence; - one main job; - a logical sequence; - no repeated caveats; - no apology-like framing; - a direct connection to the larger argument.

## Writing Principles

Lead with the claim. Start paragraphs with the point, not with a caveat.

Use positive scope. State what the text examines, explains, tests, compares, or contributes.

Strengthen with evidence, not apology. When a claim feels too broad, improve the concepts, evidence, causal logic, scope, or paragraph structure instead of adding protective caveats.

Keep one paragraph, one job. Do not mix argument, caveat, apology, exception, and clarification in the same paragraph.

Use contrast only when the contrast itself is part of the argument. Avoid reflexive "not X but Y", "rather than", "instead of", "to be clear", and "it should be noted that" structures.

## Preferred Patterns

Use patterns like:

- "This paper examines..." - "This study shows..." - "The analysis focuses on..." - "The evidence indicates..." - "This design allows..." - "The results suggest..." - "The central contribution is..." - "This section explains..." - "The argument proceeds in three steps..." - "In this setting, X shapes Y by..."

## Discouraged Patterns

Avoid these unless they are necessary for accuracy:

- "This paper does not claim..." - "We do not attempt to..." - "This is not to say that..." - "This should not be taken to mean..." - "The goal is not X but Y..." - "Rather than arguing X, this paper argues Y..." - "Although this study has limitations..." - "Of course, this does not fully capture..." - "It is worth noting that..." - "To be clear..."

## Examples

Defensive:

> We do not claim that these cases are representative of all contexts.

Stronger:

> The cases show how the mechanism operates across three institutional settings.

Defensive:

> This paper is not intended to provide a comprehensive theory of platform governance, but rather to examine one specific mechanism.

Stronger:

> This paper identifies a mechanism through which platform governance reshapes participation.

Defensive:

> This does not mean that policy design alone determines implementation outcomes.

Stronger:

> Implementation outcomes depend on how policy design interacts with administrative capacity.

Defensive:

> While the sample is limited and cannot capture every variation, it still offers useful insights.

Stronger:

> The sample captures the variation most relevant to the study's theoretical question.

Defensive:

> We are not arguing that this model is superior in every situation.

Stronger:

> The model is most useful when the task requires interpretable comparisons across cases.

## Final Pass

Before producing the final answer, remove any sentence that exists mainly to protect against a hypothetical objection rather than to advance the text. Deliver text that is concise, direct, confident, logically organized, and free of unnecessary disclaimers.

Technical details

Version
1.0.0
License
MIT
Last updated
Aug 24, 2026
Published
Aug 24, 2026

Decision snapshot

Fallback candidate

67
Ready
Prototype
Stage

recent repository activity

Audit

Install review

Install and adoption review

83
Safe to try
Security
88/100
Maintenance
100/100
Install
92/100
Open full auditView eval report

Agent-proven evidence

Agent-proven evidence

Outcome reports after resolve, review, install, and one narrow run.

0
Proven
Needs first agent runAuto-install: review firstLast: Unknown
Success rate
Recent failure
Outcomes
0
Output quality
Failed
0
Not relevant
0
Installs
0
Risk blocked
0
Setup needed
0
Production
0

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

Add to agent workflow

Free and open source. Review the report before installing into production agents.

Growth loop

Share kit

X

Scenario-led draft for anti-defensive-writing, ready for a manual X post.

Curator note
anti-defensive-writing: Reduce defensive writing in drafts and revisions by removing unnecessary caveats, disclaimers...

136 stars

https://www.openagentskill.com/skills/kiterlin-anti-defensive-writing?ref=x
Open X draft
Optional reply with install command
Listing + install path for anti-defensive-writing:
https://www.openagentskill.com/skills/kiterlin-anti-defensive-writing?ref=x

Install: npx skills add Kiterlin/anti-defensive-writing --skill anti-defensive-writing

Listing source

Registry indexed

Claimable

This listing was indexed from public sources and is not marked official until a maintainer claim is approved.

Creator
Kiterlin
Indexed by
OpenAgentSkill community index

Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.

Claim this skill

Owner claim

Claim this skill listing

This Registry indexed listing is attributed to Kiterlin 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

Add the evidence badges to your README

Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.

[![Listed on OpenAgentSkill](https://www.openagentskill.com/api/badge/kiterlin-anti-defensive-writing?metric=listed&label=Listed)](https://www.openagentskill.com/skills/kiterlin-anti-defensive-writing)
[![OpenAgentSkill Trust](https://www.openagentskill.com/api/badge/kiterlin-anti-defensive-writing?metric=trust&label=Trust)](https://www.openagentskill.com/skills/kiterlin-anti-defensive-writing)
[![OpenAgentSkill Audit](https://www.openagentskill.com/api/badge/kiterlin-anti-defensive-writing?metric=audit&label=Audit)](https://www.openagentskill.com/skills/kiterlin-anti-defensive-writing/audit)
[![Agent Proven](https://www.openagentskill.com/api/badge/kiterlin-anti-defensive-writing?metric=proven&label=Agent%20Proven)](https://www.openagentskill.com/skills/kiterlin-anti-defensive-writing)

Author

K

Kiterlin

@kiterlin

Platform fit

Health signals

GitHub stars
136
Quality score
39/100
Last GitHub push
Aug 24, 2026
Framework hints
Unknown
OpenAgentSkill views
0
Install copies
0
Outbound clicks
0

Community signal

Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.

Trust & safety

Sandbox only

73
  • GitHub adoption136 GitHub starsINFO
  • Stars/forks activity136 stars, 3 forks; issue activity unavailable in current metadataCHECK
  • Recent maintenancePushed todayPASS
  • License clarityMITPASS
  • README/SKILL.md completenessMetadata includes enough usage and workflow contextPASS
  • Dependency/runtime riskno major dependency risk hints in public metadataPASS