failure-library

Tinjau · 64
Diindeks di Registry

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.

Verified installs0
Star28
Versi1.0.0
Kualitas61/100 · Menjanjikan
Kepercayaan64/100 · Hanya sandbox
Audit76/100 · Perlu ditinjau

Profil aset

Riset dan pekerjaan pengetahuan

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

Lihat kategori

Skenario

Agent riset

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

Kecocokan Agent

Claude Code + CLI + Codex

Cocok untuk Codex, Claude Code, Cursor, CLI, atau Agent khusus.

Pasang

Siap

npx skills add Deupaxx/EveryDay-Writer --skill failure-library

Pemeliharaan

Terkini

2 hari sejak push

Risiko

Perlu ditinjau

Financial research output is not financial advice; require human review before any live investment decision

Kualitas GitHub

28

61/100 Kualitas · 72/100 Kepercayaan

Tag cakupan

RisetAgent risetagent-skill

Catatan ulasan

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.

Kartu adopsi Agent

Kepercayaan, audit, dan kesiapan pemasangan dalam sekali lihat

Skor ini menggabungkan metadata repositori publik, sinyal ulasan OpenAgentSkill, kebaruan pemeliharaan, dan kesiapan pemasangan. Ini adalah sinyal shortlist, bukan pengganti peninjauan manusia.

Kualitas

Menjanjikan
61

Useful candidate, but compare it with alternatives before adopting.

Kepercayaan

Hanya sandbox
64

Kandidat berguna dengan sinyal kepercayaan yang kurang atau bercampur. Gunakan di ruang kerja terisolasi hingga loop hasil membuktikan kecocokan tugas.

Audit

Perlu ditinjau
76

Tinjauan yang dapat dibaca mesin tentang kesiapan pemasangan, metadata keamanan, pemeliharaan, dan risiko adopsi.

Trust Score OpenAgentSkill v5

Tinjauan manusia sebelum pemasangan

Jalankan hanya dalam sandbox dan bandingkan alternatif terdekat sebelum digunakan untuk kerja nyata.

CodexClaude CodeCursorOpenAgentSkill CLI

Star

28 star GitHub

Aktivitas repositori

28 star dan 5 fork

Pemeliharaan

2 hari sejak push

Lisensi

MIT

Pasang

npx skills add Deupaxx/EveryDay-Writer --skill failure-library

Keamanan pemasangan

Jalur pemasangan paket atau runtime standar

Cakupan izin

Akses sistem file atau dokumen

Hasil Agent

Belum ada data hasil Agent

Dokumentasi

Konteks README/SKILL.md kuat

Ringkasan risiko

Tinjau sebelum produksi

  • 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

Kesiapan pemasangan

Jalur pemasangan tersedia

  • Jalur pemasangan tersedia
  • Bukti repositori tersedia
  • Lisensi dinyatakan
  • Belum ada bukti hasil Agent-Proven

Metadata yang dapat dibaca Agent

Data keputusan yang dapat dibaca mesin untuk skill ini.

Gunakan blok ini atau JSON tersemat untuk memutuskan apakah Agent perlu memasang skill ini, memilih alternatif, atau meminta tinjauan manusia terlebih dahulu.

Buka JSON

Tugas yang sesuai

  • Alur kerja Agent riset
  • Tim Claude Code
  • builders willing to evaluate younger projects
  • Sumber pencarian

Agent yang sesuai

CodexClaude CodeCursorOpenAgentSkill CLICLI

Keputusan pemasangan

Perintah
npx skills add Deupaxx/EveryDay-Writer --skill failure-library
Kebijakan
Tinjau
Tinjauan manusia
Ya

Kepercayaan dan risiko

Kepercayaan
64/100
Audit
76/100
Tingkat risiko
Perlu ditinjau

Lingkar hasil

Endpoint
/api/agent/outcome
ID event
resolve
Hasil
5

Perintah pemasangan

npx skills add Deupaxx/EveryDay-Writer --skill failure-library

Jangan gunakan ketika

  • Tim yang membutuhkan SLA dengan dukungan vendor
  • 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

Keamanan Agent v2

56/100 · Tinjau sebelum memasang

EksperimentalTinjau

Sparse or mixed signals. Useful for discovery, but not for autonomous installation.

Test manually in an isolated workspace and compare against safer alternatives.

Selesaikan via API

Sedang

Browser automation

Skill may drive a browser or interact with web pages.

Sedang

Akses jaringan

Skill kemungkinan mengambil halaman jarak jauh, API, repositori, atau layanan eksternal.

Sedang

Akses sistem file

Skill dapat membaca atau menulis file proyek, dokumen, artefak yang dihasilkan, atau status workspace lokal.

  • Financial research output is not financial advice; require human review before any live investment decision

Target pemasangan

Pasang skill ini di alur Agent Anda

Gunakan endpoint publik untuk mengambil perintah, checklist keamanan, prompt target, dan tautan kanonis.

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 deupaxx-failure-library

Rencana resolusi Agent

Biarkan Agent memverifikasi kecocokan sebelum memasang.

API Resolve mengembalikan skill utama, alternatif, kebijakan keamanan, catatan audit, target pemasangan, dan prompt siap pakai.

Buka rencana teks

Agent harus memeriksa

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

Salin prompt

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.

Serah-terima Agent

Berikan jalur pemasangan kepada Agent, bukan direktori lain.

Gunakan endpoint publik untuk mengambil perintah, checklist keamanan, prompt target, dan tautan kanonis.

Buka API pemasangan

Prompt 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-library

Metadata Registry

Profil yang dapat dibaca Agent untuk pemilihan skill otomatis.

API Registry menyediakan sinyal keputusan, kepercayaan, audit, use case, dan pemasangan tanpa mengikis UI.

Buka Manifest

Kecocokan Agent

63/100

Agent riset

Platform

Claude Code

Laporan audit

Perlu ditinjau · 76/100

Tinjauan yang dapat dibaca mesin tentang kesiapan pemasangan, metadata keamanan, pemeliharaan, dan risiko adopsi.

Lihat laporan auditLihat laporan evaluasi

Panel keputusan Agent

Fallback candidate for Research agents

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

63
Kesiapan
Prototipe
Tahap

Peran di stack

Kandidat cadangan

Kecocokan utama

Agent riset

Label kepercayaan

Buat prototipe dulu

Jalur pemasangan

Perintah siap

Gunakan saat

  • Alur kerja Agent riset
  • Tim Claude Code
  • builders willing to evaluate younger projects

Bukti

  • recent repository activity
  • install command or GitHub repo available
  • profil kualitas 61/100
  • 10 event interaksi OpenAgentSkill

tinjau dulu

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

Jalur implementasi

  1. 1Pasang di Agent sandbox dan jalankan satu tugas Agent riset dari awal hingga akhir.
  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.

Profil kepercayaan

Hanya sandbox

Kandidat berguna dengan sinyal kepercayaan yang kurang atau bercampur. Gunakan di ruang kerja terisolasi hingga loop hasil membuktikan kecocokan tugas.

64
Trust Score OpenAgentSkill

Adopsi GitHub

Periksa

28 star GitHub

Aktivitas star/fork

Periksa

28 star dan 5 fork; aktivitas issue tidak tersedia dalam metadata saat ini

Pemeliharaan terbaru

Lulus

2 hari sejak push

Kejelasan lisensi

Lulus

MIT

Sinyal positif

  • Tinjauan AI disetujui
  • Jalur pemasangan tersedia
  • Bukti repositori tersedia
  • Repositori yang baru dipelihara
  • Perintah pemasangan tidak memiliki pola berisiko tinggi yang jelas
  • Loop hasil siap tetapi membutuhkan eksekusi Agent nyata pertama

Tinjau sebelum memasang

  • 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
  • Belum ada laporan hasil Agent nyata
  • Tinjauan manusia diperlukan sebelum pemasangan tanpa pengawasan

Tindakan yang disarankan

Jalankan hanya dalam sandbox dan bandingkan alternatif terdekat sebelum digunakan untuk kerja nyata.

Profil kualitas

Menjanjikan kandidat untuk alur kerja Agent

Useful candidate, but compare it with alternatives before adopting.

61
Star GitHub
28
Keterkinian
2 hari lalu
Siap dipasang
Ya
Lisensi
MIT
Tinjau sebelum memasang: 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.

Kecocokan alur kerja

Gunakan skill ini pada skenario berikut

Kecocokan alur kerja

Tambahkan ke alur kerja lengkap

Daftar alternatif

Bandingkan sebelum memasang

Similar skills that may fit this task.

Bandingkan semua

Ringkasan

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

Detail teknis

Versi
1.0.0
Lisensi
MIT
Pembaruan terakhir
20 Agu 2026
Diterbitkan
20 Agu 2026

Ringkasan keputusan

Kandidat cadangan

63
Siap
Prototipe
Tahap

recent repository activity

Audit

Tinjauan pemasangan

Tinjauan pemasangan dan adopsi

76
Perlu ditinjau
Keamanan
80/100
Pemeliharaan
100/100
Pasang
92/100
Buka audit lengkapLihat laporan evaluasi

Bukti tervalidasi Agent

Bukti tervalidasi Agent

Laporan hasil setelah resolve, tinjau, pasang, dan satu eksekusi terbatas.

0
Terbukti
Needs first agent runPasang otomatis: tinjau duluTerakhir: Tidak diketahui
Tingkat sukses
Kegagalan terbaru
Hasil
0
Kualitas output
Gagal
0
Tidak relevan
0
Pemasangan
0
Diblokir risiko
0
Perlu penyiapan
0
Produksi
0

Belum ada data hasil Agent. Eksekusi pertama dapat melaporkan keberhasilan, kebutuhan setup, blok risiko, kegagalan, atau tidak relevan melalui /api/agent/outcome.

Pasang

Tambahkan ke alur Agent

Gratis dan sumber terbuka. Tinjau laporan sebelum memasang pada Agent produksi.

Siklus pertumbuhan

Kit berbagi

X

Draf berbasis skenario untuk failure-library, siap untuk posting manual di X.

Catatan kurator
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
Buka draf X
Balasan opsional dengan perintah pemasangan
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
Buka draf balasan

Sumber listing

Diindeks Registry

Dapat diklaim

Listing ini diindeks dari sumber publik dan belum ditandai resmi hingga klaim pemelihara disetujui.

Kreator
Deupaxx
Diindeks oleh
Indeks komunitas OpenAgentSkill

Atribusi menautkan ke repositori publik atau profil kreator. Kreator dapat mengklaim listing untuk memperbarui sinyal kepemilikan.

Klaim skill ini

Klaim pemilik

Klaim listing skill ini

Listing Diindeks Registry ini dikaitkan dengan Deupaxx, tetapi belum ditandai resmi. Klaim untuk menambahkan sinyal pemilik terverifikasi dan membuat pembaruan peluncuran, pemasangan, serta audit berikutnya lebih tepercaya.

Kit backlink kreator

Tambahkan badge bukti ke README Anda

Tampilkan listing kanonis, sinyal kepercayaan dan audit saat ini, serta bukti Agent-Proven nyata di tempat pengembang mengevaluasi repositori.

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

Penulis

D

Deupaxx

@deupaxx

Kecocokan platform

Sinyal kesehatan

Star GitHub
28
Skor kualitas
33/100
Push GitHub terakhir
20 Agu 2026
Petunjuk framework
Tidak diketahui
Tampilan OpenAgentSkill
10
Salinan pemasangan
0
Klik keluar
0

Sinyal komunitas

Bagikan apakah skill ini bermanfaat untuk alur kerja Agent Anda. Masukan gabungan meningkatkan peringkat dari waktu ke waktu.

Kepercayaan & keamanan

Hanya sandbox

64
  • Adopsi GitHub28 star GitHubPeriksa
  • Aktivitas star/fork28 star dan 5 fork; aktivitas issue tidak tersedia dalam metadata saat iniPeriksa
  • Pemeliharaan terbaru2 hari sejak pushLulus
  • Kejelasan lisensiMITLulus
  • Kelengkapan README/SKILL.mdMetadata memuat konteks penggunaan dan alur kerja yang cukupLulus
  • Risiko dependensi/runtimeTidak ada petunjuk risiko dependensi besar dalam metadata publikLulus