anti-defensive-writing

审查 · 73
已收录

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
版本1.0.0
质量68/100 · 有潜力
信任73/100 · 仅限沙盒
审计83/100 · 可安全尝试

供给资产档案

研究与知识工作

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

浏览赛道

场景

研究 Agent

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

适配 Agent

Claude Code + CLI + Codex

适用于 Codex、Claude Code、Cursor、CLI 或自定义 Agent。

安装

就绪

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

维护状态

新鲜

今天有推送

风险

可安全尝试

Quality score needs review

GitHub 质量

136

68/100 质量 · 81/100 信任

覆盖标签

研究研究 Agent自动化agent-skill

审查说明

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

Agent 采用评分卡

一眼查看信任、审计与安装准备度

这些分数综合公开仓库元数据、OpenAgentSkill 审查信号、维护新鲜度与安装准备度。它用于候选筛选,不替代人工审查。

质量

有潜力
68

有用的候选项,但采用前应与替代方案比较。

信任

仅限沙盒
73

有用但信任信号不足或混杂的候选项。在结果闭环证明任务匹配前,请保持在隔离工作区内使用。

审计

可安全尝试
83

对安装准备度、安全元数据、维护情况与采用风险的机器可读审查。

OpenAgentSkill 信任评分 v5

安装前需人工审查

仅在沙盒中运行,并在用于真实工作前比较接近的替代方案。

CodexClaude CodeCursorOpenAgentSkill CLI

Stars

136 个 GitHub Stars

仓库活跃度

136 个 Star,3 个 Fork

维护状态

今天有推送

许可证

MIT

安装

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

安装安全性

标准软件包或运行时安装路径

权限范围

公开元数据中未发现高风险权限范围

Agent 结果

暂未有 Agent 结果数据

文档

README/SKILL.md 上下文充分

风险摘要

生产前审查

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

安装准备度

安装路径可用

  • 安装路径可用
  • 仓库证据可用
  • 已声明许可证
  • 暂无 Agent 验证结果证据

Agent 可读元数据

这个 Skill 的机器可读决策数据。

使用此区块或内嵌 JSON 判断 Agent 是否应安装该 Skill、选择替代方案,或先请求人工审查。

打开 JSON

适用任务

  • 研究 Agent 工作流
  • Claude Code 团队
  • builders willing to evaluate younger projects
  • 检索来源

适用 Agent

CodexClaude CodeCursorOpenAgentSkill CLICLI

安装决策

命令
npx skills add Kiterlin/anti-defensive-writing --skill anti-defensive-writing
策略
审查
人工审查

信任与风险

信任
73/100
审计
83/100
风险级别
可安全尝试

结果闭环

端点
/api/agent/outcome
事件 ID
resolve
结果
5

安装命令

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

不适用场景

  • 需要厂商支持 SLA 的团队
  • 没有内部安全审查的高合规环境
  • 暂未有 OpenAgentSkill 使用反馈数据
  • Quality score needs review
  • Stars/forks activity: 136 stars, 3 forks; issue activity unavailable in current metadata

Agent 安全 v2

71/100 · 安装前审查

已审查审查

审计与安全信号良好,公开元数据中没有高风险权限提示。

先查看审计页面,再在沙盒工作流中允许 Agent 安装。

通过 API 解析

网络访问

Skill 可能访问远程页面、API、仓库或外部服务。

  • Quality score needs review

安装目标

在你的 Agent 工作流中安装此 Skill

通过公开安装端点获取命令、安全清单、目标提示词和该 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 解析计划

让 Agent 在安装前验证匹配度。

Resolve API 返回首选 Skill、替代方案、安全策略、审计说明、安装目标和可直接执行的提示词,无需抓取此页面。

打开文本计划

Agent 应检查

  • 从 Resolve API 检查任务匹配与替代方案。
  • 检查审计评分、信任评分和安全策略警告。
  • 检查 Codex、Claude Code、Cursor 或 CLI 的安装目标兼容性。

复制提示词

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 交接

把安装路径交给 Agent,而不是再给一个目录页。

通过公开安装端点获取命令、安全清单、目标提示词和该 Skill 的规范链接。

打开安装 API

Agent 提示词

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 元数据

用于自动选择 Skill 的 Agent 可读档案。

本页通过 Registry API 提供相同的决策、信任、审计、场景和安装信号,让 Agent 无需抓取界面即可排序。

打开 Manifest

适配 Agent

67/100

研究 Agent

平台

Claude Code

审计报告

可安全尝试 · 83/100

对安装准备度、安全元数据、维护情况与采用风险的机器可读审查。

查看审计报告查看评估报告

Agent 决策面板

Fallback candidate for Research agents

先用此 Skill 做原型验证,并保留备选方案。

67
就绪度
原型验证
阶段

栈中角色

备选候选

主要匹配

研究 Agent

信任标签

先做原型验证

安装路径

命令已就绪

适用场景

  • 研究 Agent 工作流
  • Claude Code 团队
  • builders willing to evaluate younger projects

证据

  • 仓库近期活跃
  • 已提供安装命令或 GitHub 仓库
  • 68/100 质量档案

先审查

  • 暂未有 OpenAgentSkill 使用反馈数据

实施路径

  1. 1在沙盒 Agent 中安装它,并端到端完成一次研究 Agent任务。
  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.

信任档案

仅限沙盒

有用但信任信号不足或混杂的候选项。在结果闭环证明任务匹配前,请保持在隔离工作区内使用。

73
OpenAgentSkill 信任评分

GitHub 采用度

信息

136 个 GitHub Stars

Star/Fork 活跃度

检查

136 个 Star,3 个 Fork; 当前元数据中没有议题活跃度信息

近期维护

通过

今天有推送

许可证清晰度

通过

MIT

积极信号

  • AI 审查已通过
  • 安装路径可用
  • 仓库证据可用
  • 近期维护的仓库
  • 安装命令未发现明显高风险模式
  • 结果闭环已就绪,但需要首次真实 Agent 运行

安装前审查

  • Quality score needs review
  • Stars/forks activity: 136 stars, 3 forks; issue activity unavailable in current metadata
  • 暂未有真实 Agent 结果报告
  • 无人值守安装前需要人工审查

建议操作

仅在沙盒中运行,并在用于真实工作前比较接近的替代方案。

质量档案

有潜力 适用于 Agent 工作流的候选

有用的候选项,但采用前应与替代方案比较。

68
GitHub Stars
136
新鲜度
今天
安装就绪
许可证
MIT

工作流匹配

在这些场景使用此 Skill

工作流匹配

加入完整工作流

替代方案短名单

安装前对比

可能适合该任务的相近 Skill。

对比全部

概览

--- 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.

技术详情

版本
1.0.0
许可证
MIT
最近更新
2026年8月24日
发布时间
2026年8月24日

决策摘要

备选候选

67
就绪
原型验证
阶段

仓库近期活跃

审计

安装审查

安装与采用审查

83
可安全尝试
安全性
88/100
维护状态
100/100
安装
92/100
打开完整审计查看评估报告

Agent 验证证据

Agent 验证证据

来自解析、审查、安装和一次小范围运行后的结果报告。

0
已验证
Needs first agent run自动安装: 先审查最近: 未知
成功率
近期失败
结果
0
输出质量
失败
0
不相关
0
安装次数
0
风险拦截
0
需要配置
0
生产环境
0

暂时没有 Agent 结果数据。首次 Agent 执行可以通过 /api/agent/outcome 报告成功、需要设置、风险拦截、失败或不相关。

安装

加入 Agent 工作流

免费且开源. 在生产 Agent 中安装前请先审查报告。

增长闭环

分享工具包

X

为 anti-defensive-writing 准备的场景化草稿,可手动发布到 X。

策展说明
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
打开 X 草稿
可选:带安装命令的回复
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
打开回复草稿

收录来源

Registry 收录

可认领

此列表来自公开来源,维护者认领获批前不会标记为官方。

创作者
Kiterlin
收录方
OpenAgentSkill 社区索引

归属链接指向公开仓库或创作者主页。创作者可认领列表以更新所有权信号。

认领此 Skill

所有者认领

认领此 Skill 页面

这条 Registry 收录 列表归属于 Kiterlin,但尚未标记为官方。认领后可增加已验证所有者信号,使后续发布、安装和审计更新更值得信赖。

创作者外链工具包

将证据徽章加入你的 README

在开发者评估仓库的位置展示规范页面、当前信任与审计信号,以及真实的 Agent 验证证据。

[![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)

作者

K

Kiterlin

@kiterlin

平台适配

健康信号

GitHub Stars
136
质量评分
39/100
最近 GitHub 推送
2026年8月24日
框架提示
未知
OpenAgentSkill 浏览量
0
复制安装命令
0
跳转点击
0

社区信号

告诉我们这个 Skill 是否对你的 Agent 工作流有帮助。汇总反馈会持续改善排序。

信任与安全

仅限沙盒

73
  • GitHub 采用度136 个 GitHub Stars信息
  • Star/Fork 活跃度136 个 Star,3 个 Fork; 当前元数据中没有议题活跃度信息检查
  • 近期维护今天有推送通过
  • 许可证清晰度MIT通过
  • README/SKILL.md 完整度元数据包含足够的用法与工作流上下文通过
  • 依赖与运行时风险公开元数据中未发现主要依赖风险提示通过