failure-library
An annotated library of real AI writing failure patterns with full dissection. Use to teach a writer what AI slop actually looks like, diagnose why a specific passage reads as machine-written, or explain the mechanism behind a pattern.
供給アセットの概要
リサーチとナレッジ作業
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 Deupaxx/EveryDay-Writer --skill failure-library
メンテナンス
新しい
最終プッシュから 3 日
リスク
要レビュー
Financial research output is not financial advice; require human review before any live investment decision
GitHub 品質
28
61/100 品質 · 72/100 信頼
対象タグ
レビュー注記
Financial research output is not financial advice; require human review before any live investment decision · The skill references core files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the submitted skill directory, making it incomplete for its intended teaching/generation workflow.
Agent 導入スコアカード
信頼、監査、インストール準備状況を一目で確認
公開リポジトリのメタデータ、OpenAgentSkill のレビューシグナル、保守の鮮度、インストール準備状況を組み合わせたスコアです。候補選定の目安であり、人によるレビューの代替ではありません。
品質
有望有用な候補ですが、採用前に代替と比較してください。
信頼
サンドボックス限定信頼シグナルが不足または混在する有用な候補です。結果ループがタスク適合を示すまで、隔離されたワークスペースで使用してください。
監査
要レビューインストール準備、安全メタデータ、保守、採用リスクの機械可読なレビュー。
OpenAgentSkill Trust Score v5
インストール前に人のレビュー
実作業で使う前に、サンドボックスでのみ実行し、近い代替と比較してください。
スター
GitHub スター 28
リポジトリ活動
スター 28、フォーク 5
メンテナンス
最終プッシュから 3 日
ライセンス
MIT
インストール
npx skills add Deupaxx/EveryDay-Writer --skill failure-library
インストール安全性
標準パッケージまたはランタイムのインストールパス
権限範囲
ファイルシステムまたはドキュメントアクセス
Agent の成果
Agent の成果データはまだありません
ドキュメント
README/SKILL.md の文脈が十分です
リスク概要
本番前にレビュー
- The skill references core files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the submitted skill directory, making it incomplete for its intended teaching/generation workflow.
- Financial research output is not financial advice; require human review before any live investment decision.
- Low GitHub adoption signal
- Quality score needs review
インストール準備状況
インストールパスを利用可能
- インストールパスを利用できます
- リポジトリの根拠を利用できます
- ライセンスが明示されています
- Agent-Proven の成果エビデンスはまだありません
Agent 可読メタデータ
このスキルの機械可読な判断データ。
このブロックまたは埋め込み JSON を使い、Agent がこのスキルをインストールすべきか、代替を選ぶべきか、先に人のレビューを求めるべきかを判断できます。
適したタスク
- リサーチ Agent ワークフロー
- Claude Code チーム
- builders willing to evaluate younger projects
- 検索ソース
適した Agent
インストール判断
- コマンド
- npx skills add Deupaxx/EveryDay-Writer --skill failure-library
- ポリシー
- レビュー
- 人によるレビュー
- はい
信頼とリスク
- 信頼
- 64/100
- 監査
- 76/100
- リスクレベル
- 要レビュー
成果ループ
- エンドポイント
- /api/agent/outcome
- イベント ID
- resolve
- 成果
- 5
インストールコマンド
npx skills add Deupaxx/EveryDay-Writer --skill failure-library使わない場合
- ベンダー提供の SLA が必要なチーム
- production agents without a repository review
- Low GitHub adoption signal
- The skill references core files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the submitted skill directory, making it incomplete for its intended teaching/generation workflow.
- Financial research output is not financial advice; require human review before any live investment decision
Agent セーフティ v2
56/100 · インストール前にレビュー
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
中
Browser automation
Skill may drive a browser or interact with web pages.
中
ネットワークアクセス
Skill はリモートページ、API、リポジトリ、外部サービスにアクセスする可能性があります。
中
ファイルシステムアクセス
Skill はプロジェクトファイル、ドキュメント、生成物、ローカルワークスペース状態を読み書きする可能性があります。
- Financial research output is not financial advice; require human review before any live investment decision
インストール先
Agent ワークフローにこのスキルをインストール
公開インストールエンドポイントからコマンド、安全チェックリスト、対象プロンプト、正規リンクを取得します。
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 deupaxx-failure-libraryAgent 解決プラン
インストール前に Agent に適合性を検証させます。
Resolve API は第一候補、代替、安全ポリシー、監査メモ、インストール先、Agent がそのまま使えるプロンプトを返します。
JSON を開く
/api/agent/resolve?task=Use%20failure-library%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve テキスト
/api/agent/resolve?task=Use%20failure-library%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
インストール引き継ぎ
/api/skills/deupaxx-failure-library/install
Agent が確認すべきこと
- Resolve API でタスク適合と代替を確認。
- 監査・信頼スコアと安全ポリシーの警告を確認。
- Codex、Claude Code、Cursor、CLI のインストール先互換性を確認。
プロンプトをコピー
Task: Use failure-library in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20failure-library%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/deupaxx-failure-library/install
Install command: npx skills add Deupaxx/EveryDay-Writer --skill failure-library
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent 引き継ぎ
別のディレクトリではなく、インストール経路を Agent に渡します。
公開インストールエンドポイントからコマンド、安全チェックリスト、対象プロンプト、正規リンクを取得します。
インストール引き継ぎ
/api/skills/deupaxx-failure-library/install
LLM テキスト形式
/api/skills/deupaxx-failure-library/install?format=text
代替を探す
/api/skills/search?q=failure-library&limit=3
Agent プロンプト
Use failure-library for this task. Review https://www.openagentskill.com/api/skills/deupaxx-failure-library/install, then install with: npx skills add Deupaxx/EveryDay-Writer --skill failure-libraryRegistry メタデータ
自動スキル選択用の Agent 可読プロファイル。
Registry API 経由で判断、信頼、監査、ユースケース、インストールのシグナルを提供し、UI をスクレイピングせずに Agent が順位付けできます。
Agent 判断パネル
Fallback candidate for Research agents
まずこのスキルでプロトタイプを作り、代替候補を用意してください。
スタック内の役割
代替候補
主な適合
リサーチ Agent
信頼ラベル
まずプロトタイプ
インストールパス
コマンド準備済み
使う場面
- リサーチ Agent ワークフロー
- Claude Code チーム
- builders willing to evaluate younger projects
根拠
- 最近のリポジトリ活動
- インストールコマンドまたは GitHub リポジトリが利用可能
- 品質プロファイル 61/100
- OpenAgentSkill エンゲージメント 13 件
先にレビュー
- Low GitHub adoption signal
- The skill references core files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the submitted skill directory, making it incomplete for its intended teaching/generation workflow.
実装パス
- 1サンドボックスの Agent にインストールし、リサーチ Agent タスクを一度最初から最後まで実行します。
- 2Compare output quality, latency, and failure behavior against at least one alternative.
- 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.
信頼プロファイル
サンドボックス限定
信頼シグナルが不足または混在する有用な候補です。結果ループがタスク適合を示すまで、隔離されたワークスペースで使用してください。
GitHub 採用度
確認GitHub スター 28
スター/フォーク活動
確認スター 28、フォーク 5; 現在のメタデータでは Issue 活動を利用できません
最近のメンテナンス
合格最終プッシュから 3 日
ライセンスの明確さ
合格MIT
良いシグナル
- AI レビュー承認済み
- インストールパスを利用できます
- リポジトリの根拠を利用できます
- 最近保守されたリポジトリ
- インストールコマンドに明確な高リスクパターンはありません
- 成果ループは準備済みですが、最初の実行が必要です
インストール前にレビュー
- The skill references core files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the submitted skill directory, making it incomplete for its intended teaching/generation workflow.
- Financial research output is not financial advice; require human review before any live investment decision.
- Low GitHub adoption signal
- Quality score needs review
- GitHub adoption: 28 GitHub stars
- Stars/forks activity: 28 stars, 5 forks; issue activity unavailable in current metadata
- 実際の Agent 成果レポートはまだありません
- 無人インストールの前に人によるレビューが必要です
推奨アクション
実作業で使う前に、サンドボックスでのみ実行し、近い代替と比較してください。
品質プロファイル
有望 Agent ワークフロー向けの候補
有用な候補ですが、採用前に代替と比較してください。
ワークフロー適合
このスキルを使うシナリオ
Investigate faster
Research agents
I need my agent to research a topic, compare sources, and produce a concise report.
Operate local tools
Local desktop
I need my agent to operate local files and desktop apps in a repeatable workflow.
Search private knowledge
RAG and knowledge
I need my agent to build a RAG workflow over documents and retrieve reliable context.
ワークフロー適合
完全なワークフローに追加
Find, compare, and synthesize
Research report agent
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Ingest, retrieve, and cite
RAG knowledge base
A workflow for document-heavy agents that ingest files, create searchable knowledge, retrieve relevant context, and answer with grounded sources.
Operate and verify web apps
Browser QA agent
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
代替候補
インストール前に比較
このタスクに適する可能性のある類似スキル。
Last30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
Academic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
GPT Researcher
Run autonomous deep research over web and local sources
DeepResearch
Tongyi Deep Research, the Leading Open-source Deep Research Agent
概要
--- name: failure-library description: | An annotated library of real AI writing failure patterns with full dissection. Use to teach a writer what AI slop actually looks like, diagnose why a specific passage reads as machine-written, or explain the mechanism behind a pattern. license: MIT metadata: version: "0.3.0" ---
# EW Skill — Failure Library
**Reading this file as reference requires no dependencies.** It is a diagnostic document, not a generation tool.
**When using it during generation or teaching, read the full chain first:**
1. `core/anti-ai-rules.md` (read fully; Section 0 sets the standard, 0.1 sets precedence, 0.2 forbids fabrication, 9 and 10 stop over-correction) 2. `core/ai_slop_commandments.md` (mechanism reference and diagnostic checklist) 3. `core/voice-profile.md` (this writer's voice fingerprint) 4. Any `.md` files the user has dropped in `references/`
**When used as a teaching tool during generation:** Read `core/anti-ai-rules.md` before pointing to examples from this library.
---
## WHAT THIS IS
A library of real AI writing failures — not invented examples, documented patterns from actual AI-generated text found in the wild. Each entry shows the original text, names the failure pattern, and dissects exactly what went wrong.
Use this when: - A writer wants to understand what AI writing actually looks like so they can avoid it - You need to explain why a specific phrase in a draft is a failure - The writer asks "what does AI slop actually sound like?"
This is not a checklist. It is evidence. The patterns here are what `core/anti-ai-rules.md` was written to prevent.
---
## HOW TO USE THIS LIBRARY
**As a teaching reference:** When a writer produces a failure pattern, point to the relevant entry: "What you wrote matches the [Pattern Name] failure — here's what it looks like at its worst and why it breaks the reader."
**As a study tool:** Walk through the entries with the writer. The goal is not just recognition — it's internalization. A writer who can name the pattern when they read it can catch it when they write it.
**As a diagnostic:** When auditing a piece, use the failure categories here to identify what type of failure is present before naming it in the WHAT CHANGED AND WHY section.
---
## FAILURE CATEGORY 1: SIGNIFICANCE INFLATION
**The pattern:** The writing announces that something is important, significant, or part of a broader trend — instead of showing the thing and letting the reader draw that conclusion.
**Why it fails:** It tells the reader what to feel before they've felt it. It replaces specific information with a generic significance claim. The reader hasn't been shown anything; they've been instructed to be impressed.
**The tell:** Phrases like "marking a pivotal moment," "represents a significant shift," "contributing to the broader," "reflecting its continued relevance," "underscoring its importance."
**Real example:** > "The Statistical Institute of Catalonia was officially established in 1989, marking a pivotal moment in the evolution of regional statistics in Spain. The founding of Idescat represented a significant shift toward regional statistical independence."
**Why this is broken:** "Marking a pivotal moment" and "represented a significant shift" are empty phrases. They claim importance without demonstrating it. Remove them and the sentence loses nothing of substance — which is how you know they were never doing work.
**The fix:** State what actually happened. Let the significance emerge from the specifics. If the founding of a statistics institute was actually important, the importance is in what it did, not in calling it pivotal.
---
## FAILURE CATEGORY 2: TRAILING -ING ANALYSIS
**The pattern:** A sentence ends with a present-participle phrase that explains the significance of what was just said. The sentence states a fact; the trailing phrase announces what it means.
**Why it fails:** It's the writer doing the reader's job. If the fact is significant, a competent reader will draw the inference. Explaining the inference out loud collapses the gap between writer and reader, removes the reader's active participation, and signals that the writer doesn't trust their own material.
**The tell:** Sentences ending in "...highlighting its importance," "...underscoring its significance," "...reflecting the broader," "...demonstrating its lasting influence," "...emphasizing the need for."
**Real example:** > "These works are now part of the Collections of the National Museum of Education, highlighting their historical and pedagogical significance."
**Why this is broken:** The placement in the National Museum of Education already implies historical and pedagogical significance. The trailing phrase is redundant at best; at worst, it makes the reader feel managed.
**Another real example:** > "It holds a pivotal place in the East Central Railway Zone, serving as a major railway hub with historical significance. [...] contributing to the socio-economic development of the region."
**Why this is broken:** "Contributing to the socio-economic development of the region" is attached to a description of train service. It adds no information. It is the AI performing significance because it was trained to perform significance after stating facts.
**The fix:** End the sentence before the trailing phrase. Trust the fact.
---
## FAILURE CATEGORY 3: ECOSYSTEM BOILERPLATE
**The pattern:** Writing about any subject — especially biological, ecological, or community-related — includes language about its importance to the broader ecosystem, broader community, or broader trend, even when that importance is tenuous or entirely generic.
**Why it fails:** It's filler that sounds authoritative. The phrase "plays a vital role in the ecosystem" applied to a random endemic plant species is meaningless — every organism plays some role in its ecosystem by definition. The specificity is zero. The word count increases. The reader learns nothing.
**The tell:** "plays a role in the ecosystem," "contributes to the broader," "vital for ecological diversity," "preserving this species is important for," "maintaining the health of."
**Real example:** > "It plays a role in the ecosystem and contributes to Hawaii's rich cultural heritage. Preserving this endemic species is vital not only for ecological diversity but also for sustaining the cultural traditions connected to Hawaii's native flora."
**Why this is broken:** This was written about a plant called *Nototrichium divaricatum*. The ecological role is stated with zero specificity. "Vital for ecological diversity" is a content-free phrase — it could be written about any species on any island. The cultural heritage connection is invented from whole cloth.
**The fix:** Either state the specific ecological role (what this organism eats, what eats it, what depends on it) or say nothing about its ecosystem role. Generic ecological boilerplate is worse than silence.
---
## FAILURE CATEGORY 4: PROMOTIONAL LANGUAGE IN NEUTRAL CONTEXTS
**The pattern:** Writing adopts the register of a travel brochure or press release when describing a neutral subject — a town, a building, a company. Every detail is rendered in the most flattering possible light.
**Why it fails:** It's not credible. A reader encountering "nestled within the breathtaking region" in an otherwise neutral article immediately understands that they are reading generated content or promotional copy. Trust collapses.
**The tell:** "nestled," "vibrant," "rich cultural heritage," "breathtaking," "offers visitors a fascinating glimpse," "boasts," "commitment to excellence," "natural beauty," "diverse array."
**Real example:** > "Nestled within the breathtaking region of Gonder in Ethiopia, Alamata Raya Kobo stands as a vibrant town with a rich cultural heritage and a significant place within the Amhara region. From its scenic landscapes to its historical landmarks, Alamata Raya Kobo offers visitors a fascinating glimpse into the diverse tapestry of Ethiopia."
**Why this is broken:** "Nestled," "breathtaking," "vibrant," "rich cultural heritage," "fascinating glimpse," "diverse tapestry" — six promotional phrases in two sentences. None of them contain information. All of them signal that the writer is performing enthusiasm rather than conveying facts.
**The fix:** State what is true about the place. Specific details — population, what it's known for, one named feature — carry more credibility than any amount of "vibrant" and "breathtaking."
---
## FAILURE CATEGORY 5: SUPERFICIAL ANALYSIS
**The pattern:** The writing makes an analytical-sounding claim that contains no actual analysis. It connects two things with "thus," "therefore," or "demonstrating" in a way that sounds like reasoning but advances no argument.
**Why it fails:** It mimics the structure of argument without the substance. The reader follows the logical connectives ("thus," "therefore," "this demonstrates") expecting a conclusion that earns those words — and finds a statement of the obvious or a restatement of the premise.
**The tell:** "This demonstrates the ongoing relevance of," "thus proving that," "these citations illustrate [X]'s lasting influence," "thereby establishing," "this initiative was part of a broader movement."
**Real example:** > "These citations, spanning more than six decades and appearing in recognized academic publications, illustrate Blois' lasting influence in computational linguistics, grammar, and neology."
**Why this is broken:** "Illustrate lasting influence" is the conclusion of an argument that wasn't made. The citations were listed; no argument was built from them. The phrase performs analysis without performing it.
**The fix:** Either make the actual argument (here is why this specific pattern of citations indicates influence of a specific kind) or remove the analytical framing and state only the facts.
---
## FAILURE CATEGORY 6: SIGNIFICANCE BY ASSERTION
**The pattern:** The writing asserts that something is important, groundbreaking, or significant — directly, without demonstration. It does not show why the thing is significant; it announces the significance as a fact.
**Why it fails:** Significance claims without evidence are the weakest form of persuasion. Any writer can call anything important. The claim is only worth the demonstration behind it — and when there is no demonstration, the claim becomes a negative signal: the writer couldn't demonstrate significance, so they asserted it.
**The tell:** "groundbreaking," "revolutionary," "landmark," "unprecedented," "transformative," "a vital contribution to," "a significant achievement in the field of."
**Real example:** > "Her insights have also been featured in *Wired*, *Refinery29*, and other prominent media outlets."
**Why this is broken:** Media placements are listed as a substitute for demonstrating why the subject's work is significant. The list is the argument. But a list of outlet names is not an argument — it's the structure of an argument with no content inside it.
**The fix:** If the work is significant, state one specific reason it is significant — one thing it changed, one specific contribution, one concrete effect. If you can't, the significance claim should be removed.
---
## HOW TO ADD ENTRIES
When new failure patterns are identified in user output or in the wild, add them here using this format:
``` ## FAILURE CATEGORY [N]: [NAME IN CAPS]
**The pattern:** [One sentence describing the pattern]
**Why it fails:** [2–3 sentences explaining the mechanism of failure — not just that it's bad, but why it breaks]
**The tell:** [The phrases or structural signals that mark this pattern]
**Real example:** > "[Quote the actual text]"
**Why this is broken:** [Specific analysis of this example — what's missing, what's performed, what collapses]
**The fix:** [One sentence on what to do instead] ```
Real examples only. No invented examples. If you ha
技術詳細
- バージョン
- 1.0.0
- ライセンス
- MIT
- 最終更新
- 2026年8月20日
- 公開日
- 2026年8月20日
判断の要約
代替候補
最近のリポジトリ活動
Agent 実証エビデンス
Agent 実証エビデンス
Resolve、レビュー、インストール、限定実行後の成果レポート。
- 成功率
- —
- 直近の失敗
- —
- 成果
- 0
- 出力品質
- —
- 失敗
- 0
- 非該当
- 0
- インストール数
- 0
- リスクによりブロック
- 0
- 設定が必要
- 0
- 本番
- 0
Agent の実行結果はまだありません。最初の実行では /api/agent/outcome を通じて成功、設定要件、リスクによるブロック、失敗、非該当を報告できます。
成長ループ
共有キット
failure-library 用のシナリオベース草案です。X へ手動投稿できます。
failure-library: An annotated library of real AI writing failure patterns with full dissection. Use to teach a... 28 stars https://www.openagentskill.com/skills/deupaxx-failure-library?ref=x
任意:インストールコマンド付きの返信
Listing + install path for failure-library: https://www.openagentskill.com/skills/deupaxx-failure-library?ref=x Install: npx skills add Deupaxx/EveryDay-Writer --skill failure-library
掲載元
Registry により登録
この掲載は公開ソースから登録されており、メンテナー申請が承認されるまで公式として表示されません。
- 作成者
- Deupaxx
- インデックス作成者
- OpenAgentSkill コミュニティインデックス
帰属は公開リポジトリまたは作成者プロフィールにリンクされています。作成者は掲載を申請して所有権シグナルを更新できます。
このスキルを申請所有者の申請
このスキル掲載を申請
この Registry により登録 掲載は Deupaxx に帰属していますが、まだ公式として表示されていません。申請すると、確認済み所有者シグナルが追加され、今後の公開、インストール、監査更新の信頼性が高まります。
クリエイター被リンクキット
README にエビデンスバッジを追加
開発者がリポジトリを評価する場所で、正規掲載、現在の信頼・監査シグナル、実際の Agent-Proven エビデンスを表示します。
[](https://www.openagentskill.com/skills/deupaxx-failure-library)
[](https://www.openagentskill.com/skills/deupaxx-failure-library)
[](https://www.openagentskill.com/skills/deupaxx-failure-library/audit)
[](https://www.openagentskill.com/skills/deupaxx-failure-library)作者
Deupaxx
@deupaxx
プラットフォーム適合
健全性シグナル
- GitHub スター
- 28
- 品質スコア
- 33/100
- 最終 GitHub プッシュ
- 2026年8月20日
- フレームワークのヒント
- 不明
- OpenAgentSkill 閲覧数
- 12
- インストールコピー数
- 0
- 外部クリック
- 0
コミュニティシグナル
このスキルが Agent ワークフローに役立つかを共有してください。集約されたフィードバックがランキングを改善します。
信頼と安全性
サンドボックス限定
- GitHub 採用度GitHub スター 28確認
- スター/フォーク活動スター 28、フォーク 5; 現在のメタデータでは Issue 活動を利用できません確認
- 最近のメンテナンス最終プッシュから 3 日合格
- ライセンスの明確さMIT合格
- README/SKILL.md の完全性メタデータには十分な利用・ワークフロー文脈があります合格
- 依存関係/ランタイムのリスク公開メタデータに重大な依存関係リスクのヒントはありません合格
関連スキル
Last30days Skill
Research the last 30 days across Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesize a grounded brief for an AI agent.
53.5K スターAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K スターGPT Researcher
Run autonomous deep research over web and local sources
28.0K スターDeepResearch
Tongyi Deep Research, the Leading Open-source Deep Research Agent
19.8K スター