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.
Profil de l’actif
Recherche et travail de connaissance
Deep research, source comparison, literature review, RAG, knowledge search, and reports.
Scénario
Agents de recherche
I need my agent to research a topic, compare sources, and produce a concise report.
Adéquation Agent
Claude Code + CLI + Codex
Compatible avec Codex, Claude Code, Cursor, CLI ou des Agents personnalisés.
Installer
Prêt
npx skills add Deupaxx/EveryDay-Writer --skill failure-library
Maintenance
À jour
2 jours depuis le dernier push
Risque
Revue nécessaire
Financial research output is not financial advice; require human review before any live investment decision
Qualité GitHub
28
61/100 Qualité · 72/100 Confiance
Tags de couverture
Notes de revue
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.
Carte d’adoption Agent
Confiance, audit et préparation à l’installation en un coup d’œil
Ces scores combinent les métadonnées publiques du dépôt, les signaux de revue OpenAgentSkill, la fraîcheur de maintenance et la préparation à l’installation. Ils servent à présélectionner et ne remplacent pas la revue humaine.
Qualité
PrometteurUseful candidate, but compare it with alternatives before adopting.
Confiance
Sandbox uniquementCandidate utile avec des signaux de confiance incomplets ou mixtes. Gardez-la dans un espace isolé jusqu’à ce que la boucle de résultats confirme son adéquation.
Audit
Revue nécessaireRevue lisible par machine de la préparation à l’installation, des métadonnées de sécurité, de la maintenance et du risque d’adoption.
Trust Score OpenAgentSkill v5
Revue humaine avant installation
Exécutez uniquement dans un sandbox et comparez les alternatives proches avant usage réel.
Stars
28 stars GitHub
Activité du dépôt
28 stars et 5 forks
Maintenance
2 jours depuis le dernier push
Licence
MIT
Installer
npx skills add Deupaxx/EveryDay-Writer --skill failure-library
Sécurité d’installation
Chemin d’installation standard de package ou runtime
Surface de permissions
Accès au système de fichiers ou aux documents
Résultats Agent
Pas encore de données de résultats Agent
Documentation
Contexte README/SKILL.md solide
Résumé des risques
Revoir avant production
- 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
Préparation à l’installation
Chemin d’installation disponible
- Le chemin d’installation est disponible
- La preuve du dépôt est disponible
- La licence est déclarée
- Pas encore de preuve de résultat Agent-Proven
Métadonnées lisibles par Agent
Données de décision lisibles par machine pour ce skill.
Utilisez ce bloc ou le JSON intégré pour décider si un Agent doit installer ce skill, choisir une alternative ou demander d’abord une revue humaine.
Tâches adaptées
- Workflows d’Agents de recherche
- Équipes Claude Code
- builders willing to evaluate younger projects
- Sources de recherche
Agents adaptés
Décision d’installation
- Commande
- npx skills add Deupaxx/EveryDay-Writer --skill failure-library
- Politique
- Revoir
- Revue humaine
- Oui
Confiance et risque
- Confiance
- 64/100
- Audit
- 76/100
- Niveau de risque
- Revue nécessaire
Boucle de résultat
- Endpoint
- /api/agent/outcome
- ID d’événement
- resolve
- Résultats
- 5
Commande d’installation
npx skills add Deupaxx/EveryDay-Writer --skill failure-libraryNe pas utiliser quand
- Équipes qui nécessitent un SLA soutenu par le fournisseur
- 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
Skill alternatif
Last30days Skill
53.5K Stars
npx skills add mvanhorn/last30days-skill -g
Skill alternatif
Academic Research Skills
38.4K Stars
npx skills add Imbad0202/academic-research-skills
Skill alternatif
GPT Researcher
28.0K Stars
npx skills add assafelovic/gpt-researcher
Skill alternatif
DeepResearch
19.8K Stars
npx skills add Alibaba-NLP/DeepResearch
Sécurité Agent v2
56/100 · Revoir avant installation
Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
Test manually in an isolated workspace and compare against safer alternatives.
Moyen
Browser automation
Skill may drive a browser or interact with web pages.
Moyen
Accès réseau
La skill récupère probablement des pages distantes, API, dépôts ou services externes.
Moyen
Accès au système de fichiers
La skill peut lire ou écrire des fichiers de projet, documents, artefacts générés ou l’état local de l’espace de travail.
- Financial research output is not financial advice; require human review before any live investment decision
Cibles d’installation
Installer ce skill dans votre workflow Agent
Utilisez le point de terminaison public pour récupérer la commande, la checklist, les prompts et les liens canoniques.
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-libraryPlan de résolution Agent
Laissez un Agent vérifier la pertinence avant l’installation.
L’API Resolve renvoie la skill sélectionnée, des alternatives, la politique de sécurité, les notes d’audit, la cible d’installation et un prompt prêt à l’emploi.
Ouvrir JSON
/api/agent/resolve?task=Use%20failure-library%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Texte Resolve
/api/agent/resolve?task=Use%20failure-library%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Relais d’installation
/api/skills/deupaxx-failure-library/install
L’Agent doit vérifier
- 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.
Copier le 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.Relais Agent
Donnez à l’Agent le chemin d’installation, pas un autre annuaire.
Utilisez le point de terminaison public pour récupérer la commande, la checklist, les prompts et les liens canoniques.
Relais d’installation
/api/skills/deupaxx-failure-library/install
Format texte LLM
/api/skills/deupaxx-failure-library/install?format=text
Trouver des alternatives
/api/skills/search?q=failure-library&limit=3
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-libraryMétadonnées Registry
Profil lisible par Agent pour la sélection automatique de skills.
L’API Registry fournit les signaux de décision, confiance, audit, cas d’usage et installation sans analyser l’interface.
Manifest
/api/registry/manifest/deupaxx-failure-library
Texte LLM
/api/registry/manifest/deupaxx-failure-library?format=text
Alias d’installation
/api/registry/install/deupaxx-failure-library
Recommander
/api/registry/recommend?task=Use%20failure-library%20in%20an%20agent%20workflow&limit=3
Adéquation Agent
Agents de recherche
Tags de cas d’usage
Plateformes
Claude Code
Rapport d’audit
Revue nécessaire · 76/100
Revue lisible par machine de la préparation à l’installation, des métadonnées de sécurité, de la maintenance et du risque d’adoption.
Panneau de décision Agent
Fallback candidate for Research agents
Prototype with this skill first; keep a fallback candidate ready.
Rôle dans la pile
Candidate de secours
Pertinence principale
Agents de recherche
Libellé de confiance
Prototyper d’abord
Chemin d’installation
Commande prête
À utiliser lorsque
- Workflows d’Agents de recherche
- Équipes Claude Code
- builders willing to evaluate younger projects
Preuves
- recent repository activity
- install command or GitHub repo available
- profil qualité 61/100
- 9 événements OpenAgentSkill
revoir d’abord
- 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.
Chemin d’implémentation
- 1Installez-le dans un Agent en sandbox et exécutez une tâche de Agents de recherche de bout en bout.
- 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.
Profil de confiance
Sandbox uniquement
Candidate utile avec des signaux de confiance incomplets ou mixtes. Gardez-la dans un espace isolé jusqu’à ce que la boucle de résultats confirme son adéquation.
Adoption GitHub
Vérifier28 stars GitHub
Activité stars/forks
Vérifier28 stars et 5 forks; l’activité des issues n’est pas disponible dans les métadonnées actuelles
Maintenance récente
Validé2 jours depuis le dernier push
Clarté de licence
ValidéMIT
Signaux positifs
- Revue IA approuvée
- Le chemin d’installation est disponible
- La preuve du dépôt est disponible
- Dépôt maintenu récemment
- La commande d’installation ne présente aucun motif de haut risque évident
- La boucle de résultats est prête mais nécessite la première exécution réelle de l’Agent
Réviser avant installation
- 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
- Pas encore de rapports de résultats Agent réels
- Une revue humaine est requise avant une installation sans surveillance
Action recommandée
Exécutez uniquement dans un sandbox et comparez les alternatives proches avant usage réel.
Profil qualité
Prometteur candidat pour les workflows Agent
Useful candidate, but compare it with alternatives before adopting.
Adéquation au workflow
Utilisez cette skill dans ces scénarios
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.
Adéquation au workflow
Ajouter à un workflow complet
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.
Liste d’alternatives
Comparer avant installation
Similar skills that may fit this task.
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
Vue d’ensemble
--- 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
Détails techniques
- Version
- 1.0.0
- Licence
- MIT
- Dernière mise à jour
- 20 août 2026
- Publié
- 20 août 2026
Instantané de décision
Candidate de secours
recent repository activity
Audit
Revue d’installation
Revue d’installation et d’adoption
- Sécurité
- 80/100
- Maintenance
- 100/100
- Installer
- 92/100
Preuves validées par Agent
Preuves validées par Agent
Rapports après resolve, revue, installation et une exécution limitée.
- Taux de réussite
- —
- Échec récent
- —
- Résultats
- 0
- Qualité de sortie
- —
- Échecs
- 0
- Non pertinent
- 0
- Installations
- 0
- Bloqué par le risque
- 0
- Configuration requise
- 0
- Production
- 0
Aucune donnée de résultat Agent pour l’instant. La première exécution peut signaler succès, besoin de configuration, blocage de risque, échec ou non-pertinence via /api/agent/outcome.
Installer
Ajouter au workflow Agent
Gratuit et open source. Examinez le rapport avant l’installation dans des Agents de production.
Boucle de croissance
Kit de partage
Brouillon guidé par scénario pour failure-library, prêt pour une publication manuelle sur 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
Réponse facultative avec commande d’installation
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
Source de la fiche
Indexé par Registry
Cette fiche a été indexée à partir de sources publiques et n’est pas marquée officielle tant qu’une revendication de mainteneur n’est pas approuvée.
- Créateur
- Deupaxx
- Source
- Deupaxx/EveryDay-Writer
- Indexé par
- Index communautaire OpenAgentSkill
L’attribution renvoie au dépôt public ou au profil du créateur. Les créateurs peuvent revendiquer la fiche pour mettre à jour les signaux de propriété.
Revendiquer ce skillRevendication du propriétaire
Revendiquer cette fiche de skill
Cette fiche Indexé par Registry est attribuée à Deupaxx, mais n’est pas encore marquée officielle. Revendiquez-la pour ajouter un signal de propriétaire vérifié et rendre les futures mises à jour de lancement, d’installation et d’audit plus fiables.
Kit de backlinks créateur
Ajoutez les badges de preuve à votre README
Affichez la fiche canonique, les signaux actuels de confiance et d’audit, ainsi que de vraies preuves Agent-Proven là où les développeurs évaluent le dépôt.
[](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)Auteur
Deupaxx
@deupaxx
Tags
Adéquation plateforme
Signaux de santé
- Stars GitHub
- 28
- Score de qualité
- 33/100
- Dernier push GitHub
- 20 août 2026
- Indications de framework
- Inconnu
- Vues OpenAgentSkill
- 9
- Copies d’installation
- 0
- Clics sortants
- 0
Signal de communauté
Indiquez si ce skill semble utile à votre workflow Agent. Les retours agrégés améliorent le classement au fil du temps.
Confiance et sécurité
Sandbox uniquement
- Adoption GitHub28 stars GitHubVérifier
- Activité stars/forks28 stars et 5 forks; l’activité des issues n’est pas disponible dans les métadonnées actuellesVérifier
- Maintenance récente2 jours depuis le dernier pushValidé
- Clarté de licenceMITValidé
- Complétude README/SKILL.mdLes métadonnées incluent suffisamment de contexte d’usage et de workflowValidé
- Risque dépendances/runtimeAucun indice majeur de risque de dépendance dans les métadonnées publiquesValidé
Skills associés
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 StarsAcademic Research Skills
Academic Research Skills for Claude Code: research → write → review → revise → finalize
38.4K StarsGPT Researcher
Run autonomous deep research over web and local sources
28.0K StarsDeepResearch
Tongyi Deep Research, the Leading Open-source Deep Research Agent
19.8K Stars