failure-library

Prüfen · 64
Im Registry indexiert

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
Stars28
Version1.0.0
Qualität61/100 · Vielversprechend
Vertrauen64/100 · Nur Sandbox
Audit76/100 · Prüfung nötig

Asset-Profil

Recherche und Wissensarbeit

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

Bereich ansehen

Szenario

Recherche-Agents

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

Agent-Fit

Claude Code + CLI + Codex

Geeignet für Codex, Claude Code, Cursor, CLI oder benutzerdefinierte Agents.

Installieren

Bereit

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

Wartung

Aktuell

3 Tage seit dem letzten Push

Risiko

Prüfung nötig

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

GitHub-Qualität

28

61/100 Qualität · 72/100 Vertrauen

Abdeckungs-Tags

RechercheRecherche-Agentsagent-skill

Review-Notizen

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

Vertrauen, Audit und Installationsbereitschaft auf einen Blick

Diese Werte kombinieren öffentliche Repository-Metadaten, OpenAgentSkill-Reviewsignale, Wartungsaktualität und Installationsbereitschaft. Sie helfen bei der Vorauswahl, ersetzen aber keine menschliche Prüfung.

Qualität

Vielversprechend
61

Useful candidate, but compare it with alternatives before adopting.

Vertrauen

Nur Sandbox
64

Nützlicher Kandidat mit fehlenden oder gemischten Vertrauenssignalen. Bis der Ergebniszyklus die Passung belegt, in einem isolierten Arbeitsbereich verwenden.

Audit

Prüfung nötig
76

Maschinenlesbare Prüfung von Installationsbereitschaft, Sicherheitsmetadaten, Wartung und Akzeptanzrisiko.

OpenAgentSkill Trust Score v5

Menschliche Prüfung vor Installation

Nur in einer Sandbox ausführen und nahe Alternativen vergleichen, bevor sie produktiv eingesetzt wird.

CodexClaude CodeCursorOpenAgentSkill CLI

Stars

28 GitHub-Stars

Repository-Aktivität

28 Stars und 5 Forks

Wartung

3 Tage seit dem letzten Push

Lizenz

MIT

Installieren

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

Installationssicherheit

Standard-Paket- oder Laufzeit-Installationspfad

Berechtigungsfläche

Dateisystem- oder Dokumentzugriff

Agent-Ergebnisse

Noch keine Agent-Ergebnisdaten

Dokumentation

Starker README/SKILL.md-Kontext

Risikoübersicht

Vor Produktion prüfen

  • 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

Installationsbereitschaft

Installationspfad verfügbar

  • Installationspfad ist verfügbar
  • Repository-Belege sind verfügbar
  • Lizenz ist angegeben
  • Noch keine Agent-Proven-Ergebnisbelege

Agent-lesbare Metadaten

Maschinenlesbare Entscheidungsdaten für diesen Skill.

Nutze diesen Block oder das eingebettete JSON, um zu entscheiden, ob ein Agent diesen Skill installieren, eine Alternative wählen oder zuerst menschliche Prüfung anfordern soll.

JSON öffnen

Geeignete Aufgaben

  • Research-Agent-Workflows
  • Claude-Code-Teams
  • builders willing to evaluate younger projects
  • Suchquellen

Geeignete Agents

CodexClaude CodeCursorOpenAgentSkill CLICLI

Installationsentscheidung

Befehl
npx skills add Deupaxx/EveryDay-Writer --skill failure-library
Richtlinie
Prüfen
Menschliche Prüfung
Ja

Vertrauen und Risiko

Vertrauen
64/100
Audit
76/100
Risikoebene
Prüfung nötig

Ergebnis-Loop

Endpoint
/api/agent/outcome
Event-ID
resolve
Ergebnisse
5

Installationsbefehl

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

Nicht verwenden, wenn

  • Teams, die ein vom Anbieter unterstütztes SLA benötigen
  • 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-Sicherheit v2

56/100 · Vor Installation prüfen

ExperimentellPrüfen

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

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

Per API auflösen

Mittel

Browser automation

Skill may drive a browser or interact with web pages.

Mittel

Netzwerkzugriff

Die Skill ruft wahrscheinlich Remote-Seiten, APIs, Repositories oder externe Dienste ab.

Mittel

Dateisystemzugriff

Die Skill kann Projektdateien, Dokumente, generierte Artefakte oder den lokalen Arbeitsbereich lesen oder schreiben.

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

Installationsziele

Diesen Skill im Agent-Workflow installieren

Über den öffentlichen Endpunkt erhältst du Befehl, Sicherheitscheckliste, Ziel-Prompts und kanonische Links.

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

Agent-Auflösungsplan

Lass einen Agent die Eignung vor der Installation prüfen.

Die Resolve API liefert die beste Skill, Alternativen, Sicherheitsrichtlinien, Auditnotizen, Installationsziel und einen direkt nutzbaren Prompt.

Textplan öffnen

Agent sollte prüfen

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

Prompt kopieren

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

Gib dem Agent den Installationspfad, nicht noch ein Verzeichnis.

Über den öffentlichen Endpunkt erhältst du Befehl, Sicherheitscheckliste, Ziel-Prompts und kanonische Links.

Installations-API öffnen

Agent-Prompt

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

Registry-Metadaten

Agent-lesbares Profil für die automatische Skill-Auswahl.

Die Registry API stellt Entscheidungs-, Vertrauens-, Audit-, Use-Case- und Installationssignale ohne UI-Scraping bereit.

Manifest öffnen

Agent-Fit

63/100

Recherche-Agents

Plattformen

Claude Code

Audit-Bericht

Prüfung nötig · 76/100

Maschinenlesbare Prüfung von Installationsbereitschaft, Sicherheitsmetadaten, Wartung und Akzeptanzrisiko.

Audit-Bericht ansehenEval-Bericht ansehen

Agent-Entscheidungspanel

Fallback candidate for Research agents

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

63
Bereitschaft
Prototyp
Phase

Rolle im Stack

Fallback-Kandidat

Primäre Eignung

Recherche-Agents

Vertrauenslabel

Zuerst prototypisieren

Installationspfad

Befehl bereit

Verwenden wenn

  • Research-Agent-Workflows
  • Claude-Code-Teams
  • builders willing to evaluate younger projects

Evidenz

  • recent repository activity
  • install command or GitHub repo available
  • Qualitätsprofil 61/100
  • 10 OpenAgentSkill-Interaktionen

zuerst prüfen

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

Implementierungspfad

  1. 1Installieren Sie es in einem Sandbox-Agent und führen Sie eine Recherche-Agents-Aufgabe vollständig aus.
  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.

Vertrauensprofil

Nur Sandbox

Nützlicher Kandidat mit fehlenden oder gemischten Vertrauenssignalen. Bis der Ergebniszyklus die Passung belegt, in einem isolierten Arbeitsbereich verwenden.

64
OpenAgentSkill Trust Score

GitHub-Akzeptanz

Prüfen

28 GitHub-Stars

Star-/Fork-Aktivität

Prüfen

28 Stars und 5 Forks; Issue-Aktivität ist in den aktuellen Metadaten nicht verfügbar

Aktuelle Wartung

Bestanden

3 Tage seit dem letzten Push

Lizenzklarheit

Bestanden

MIT

Positive Signale

  • KI-Prüfung genehmigt
  • Installationspfad ist verfügbar
  • Repository-Belege sind verfügbar
  • Kürzlich gewartetes Repository
  • Der Installationsbefehl weist kein offensichtliches Hochrisikomuster auf
  • Ergebniszyklus ist bereit, benötigt aber den ersten echten Agent-Lauf

Vor Installation prüfen

  • 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
  • Noch keine echten Agent-Ergebnisberichte
  • Vor unbeaufsichtigter Installation ist menschliche Prüfung erforderlich

Empfohlene Aktion

Nur in einer Sandbox ausführen und nahe Alternativen vergleichen, bevor sie produktiv eingesetzt wird.

Qualitätsprofil

Vielversprechend Kandidat für Agent-Workflows

Useful candidate, but compare it with alternatives before adopting.

61
GitHub-Stars
28
Aktualität
vor 3 Tagen
Installationsbereit
Ja
Lizenz
MIT
Vor Installation prüfen: 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.

Workflow-Eignung

Diese Skill in diesen Szenarien nutzen

Workflow-Eignung

Zum vollständigen Workflow hinzufügen

Alternativen-Shortlist

Vor Installation vergleichen

Similar skills that may fit this task.

Alle vergleichen

Übersicht

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

Technische Details

Version
1.0.0
Lizenz
MIT
Letzte Aktualisierung
20. Aug. 2026
Veröffentlicht
20. Aug. 2026

Entscheidungsübersicht

Fallback-Kandidat

63
Bereit
Prototyp
Phase

recent repository activity

Audit

Installationsprüfung

Installations- und Adoptionsprüfung

76
Prüfung nötig
Sicherheit
80/100
Wartung
100/100
Installieren
92/100
Vollständiges Audit öffnenEval-Bericht ansehen

Von Agent belegte Evidenz

Von Agent belegte Evidenz

Ergebnisberichte nach Resolve, Prüfung, Installation und einem begrenzten Lauf.

0
Belegt
Needs first agent runAuto-Installation: zuerst prüfenLetzter: Unbekannt
Erfolgsrate
Letzter Fehler
Ergebnisse
0
Ausgabequalität
Fehlgeschlagen
0
Nicht relevant
0
Installationen
0
Durch Risiko blockiert
0
Einrichtung erforderlich
0
Produktion
0

Noch keine Agent-Ergebnisdaten. Der erste Lauf kann Erfolg, Einrichtungsbedarf, Risikoblockaden, Fehler oder Irrelevanz über /api/agent/outcome melden.

Installieren

Zum Agent-Workflow hinzufügen

Kostenlos und Open Source. Bericht vor der Installation in Produktions-Agents prüfen.

Wachstums-Loop

Share-Kit

X

Szenariobasierter Entwurf für failure-library, bereit für einen manuellen X-Post.

Kuratorenhinweis
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
X-Entwurf öffnen
Optionale Antwort mit Installationsbefehl
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
Antwortentwurf öffnen

Quelle des Eintrags

Registry-indexiert

Beanspruchbar

Dieser Eintrag wurde aus öffentlichen Quellen indexiert und ist erst nach Genehmigung eines Maintainer-Anspruchs offiziell.

Ersteller
Deupaxx
Indexiert von
OpenAgentSkill Community-Index

Die Zuordnung verlinkt auf das öffentliche Repository oder Creator-Profil. Creator können den Eintrag beanspruchen, um Eigentümersignale zu aktualisieren.

Diesen Skill beanspruchen

Eigentümeranspruch

Diesen Skill-Eintrag beanspruchen

Dieser Registry-indexiert-Eintrag wird Deupaxx zugeschrieben, ist aber noch nicht offiziell markiert. Beanspruche ihn, um ein verifiziertes Eigentümersignal hinzuzufügen und künftige Launch-, Installations- und Audit-Updates vertrauenswürdiger zu machen.

Creator-Backlink-Kit

Evidenz-Badges in deine README einfügen

Zeige den kanonischen Eintrag, aktuelle Vertrauens- und Audit-Signale sowie echte Agent-Proven-Evidenz dort, wo Entwickler das Repository bewerten.

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

Autor

D

Deupaxx

@deupaxx

Plattform-Fit

Gesundheitssignale

GitHub-Stars
28
Qualitätswert
33/100
Letzter GitHub-Push
20. Aug. 2026
Framework-Hinweise
Unbekannt
OpenAgentSkill-Aufrufe
10
Installationskopien
0
Externe Klicks
0

Community-Signal

Teile mit, ob dieser Skill für deinen Agent-Workflow nützlich ist. Zusammengefasstes Feedback verbessert das Ranking im Laufe der Zeit.

Vertrauen & Sicherheit

Nur Sandbox

64
  • GitHub-Akzeptanz28 GitHub-StarsPrüfen
  • Star-/Fork-Aktivität28 Stars und 5 Forks; Issue-Aktivität ist in den aktuellen Metadaten nicht verfügbarPrüfen
  • Aktuelle Wartung3 Tage seit dem letzten PushBestanden
  • LizenzklarheitMITBestanden
  • README/SKILL.md-VollständigkeitMetadaten enthalten ausreichend Nutzungs- und Workflow-KontextBestanden
  • Abhängigkeits-/LaufzeitrisikoKeine wesentlichen Abhängigkeitsrisikohinweise in öffentlichen MetadatenBestanden