failure-library

검토 · 64
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
스타28
버전1.0.0
품질61/100 · 유망
신뢰64/100 · 샌드박스 전용
감사76/100 · 검토 필요

공급 자산 프로필

리서치 및 지식 작업

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

트랙 보기

시나리오

리서치 Agent

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

Agent 적합도

Claude Code + CLI + Codex

Codex, Claude Code, Cursor, CLI 또는 맞춤형 Agent에 적합합니다.

설치

준비됨

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

유지보수

최신

마지막 푸시 후 2일

위험

검토 필요

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

GitHub 품질

28

61/100 품질 · 72/100 신뢰

커버리지 태그

리서치리서치 Agentagent-skill

검토 메모

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 검토 신호, 유지보수 최신성, 설치 준비 상태를 결합합니다. 후보 선정 신호일 뿐, 사람의 검토를 대체하지 않습니다.

품질

유망
61

유용한 후보이지만 채택 전에 대안과 비교하세요.

신뢰

샌드박스 전용
64

신뢰 신호가 부족하거나 혼재된 유용한 후보입니다. 결과 루프가 작업 적합성을 입증할 때까지 격리된 작업 공간에서 사용하세요.

감사

검토 필요
76

설치 준비 상태, 보안 메타데이터, 유지보수 및 채택 위험에 대한 기계 판독형 검토입니다.

OpenAgentSkill 신뢰 점수 v5

설치 전 사람 검토

실제 작업에 사용하기 전 샌드박스에서만 실행하고 유사 대안과 비교하세요.

CodexClaude CodeCursorOpenAgentSkill CLI

스타

GitHub 스타 28

저장소 활동

스타 28, 포크 5

유지보수

마지막 푸시 후 2일

라이선스

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 검증 결과 근거가 없습니다

Agent 읽기용 메타데이터

이 스킬의 기계 판독형 의사결정 데이터.

이 블록 또는 포함된 JSON을 사용해 Agent가 이 스킬을 설치할지, 대안을 고를지, 먼저 사람의 검토를 요청할지 판단할 수 있습니다.

JSON 열기

적합한 작업

  • 리서치 Agent 워크플로
  • Claude Code 팀
  • builders willing to evaluate younger projects
  • 검색 소스

적합한 Agent

CodexClaude CodeCursorOpenAgentSkill CLICLI

설치 결정

명령어
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.

API로 해결

중간

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 워크플로에 이 스킬 설치

공개 설치 엔드포인트에서 명령어, 안전 체크리스트, 대상 프롬프트와 정규 링크를 가져옵니다.

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 해결 계획

설치 전에 Agent가 적합성을 검증하게 하세요.

Resolve API는 최우선 스킬, 대안, 안전 정책, 감사 메모, 설치 대상 및 Agent가 페이지를 스크래핑하지 않고 사용할 수 있는 프롬프트를 반환합니다.

텍스트 계획 열기

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

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

Registry 메타데이터

자동 스킬 선택을 위한 Agent 읽기용 프로필.

Registry API를 통해 동일한 결정, 신뢰, 감사, 사용 사례, 설치 신호를 제공하므로 Agent가 UI를 스크래핑하지 않고도 순위를 매길 수 있습니다.

Manifest 열기

Agent 적합도

63/100

리서치 Agent

플랫폼

Claude Code

감사 보고서

검토 필요 · 76/100

설치 준비 상태, 보안 메타데이터, 유지보수 및 채택 위험에 대한 기계 판독형 검토입니다.

감사 보고서 보기평가 보고서 보기

Agent 결정 패널

Fallback candidate for Research agents

먼저 이 스킬로 프로토타입을 만들고 대체 후보를 준비하세요.

63
준비 상태
프로토타입
단계

스택 내 역할

대체 후보

주요 적합도

리서치 Agent

신뢰 라벨

먼저 프로토타입

설치 경로

명령어 준비됨

사용 시점

  • 리서치 Agent 워크플로
  • Claude Code 팀
  • builders willing to evaluate younger projects

근거

  • 최근 저장소 활동
  • 설치 명령 또는 GitHub 저장소를 사용할 수 있습니다
  • 품질 프로필 61/100
  • OpenAgentSkill 상호작용 10건

먼저 검토

  • 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. 1샌드박스 Agent에 설치하고 리서치 Agent 작업을 처음부터 끝까지 한 번 실행하세요.
  2. 2Compare output quality, latency, and failure behavior against at least one alternative.
  3. 3Promote it into production only after reviewing repository permissions, license, and maintenance signals.

신뢰 프로필

샌드박스 전용

신뢰 신호가 부족하거나 혼재된 유용한 후보입니다. 결과 루프가 작업 적합성을 입증할 때까지 격리된 작업 공간에서 사용하세요.

64
OpenAgentSkill 신뢰 점수

GitHub 채택도

확인

GitHub 스타 28

스타/포크 활동

확인

스타 28, 포크 5; 현재 메타데이터에서 이슈 활동을 확인할 수 없습니다

최근 유지보수

통과

마지막 푸시 후 2일

라이선스 명확성

통과

MIT

긍정 신호

  • AI 검토 승인됨
  • 설치 경로를 사용할 수 있습니다
  • 저장소 근거를 사용할 수 있습니다
  • 최근 유지보수된 저장소
  • 설치 명령에서 뚜렷한 고위험 패턴이 발견되지 않았습니다
  • 결과 루프는 준비되었지만 첫 실제 Agent 실행이 필요합니다

설치 전 검토

  • 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 워크플로용 후보

유용한 후보이지만 채택 전에 대안과 비교하세요.

61
GitHub 스타
28
최신성
2일 전
설치 준비됨
라이선스
MIT
설치 전 검토: 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.

워크플로 적합도

이 스킬을 사용할 시나리오

워크플로 적합도

완전한 워크플로에 추가

대안 후보

설치 전 비교

이 작업에 적합할 수 있는 유사 스킬입니다.

모두 비교

개요

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

결정 스냅샷

대체 후보

63
준비됨
프로토타입
단계

최근 저장소 활동

감사

설치 검토

설치 및 채택 검토

76
검토 필요
보안
80/100
유지보수
100/100
설치
92/100
전체 감사 열기평가 보고서 보기

Agent 검증 증거

Agent 검증 증거

Resolve, 검토, 설치 및 한 번의 제한된 실행 후 결과 보고서입니다.

0
검증됨
Needs first agent run자동 설치: 먼저 검토최근: 알 수 없음
성공률
최근 실패
결과
0
출력 품질
실패
0
관련 없음
0
설치
0
위험 차단
0
설정 필요
0
프로덕션
0

아직 Agent 결과 데이터가 없습니다. 첫 실행은 /api/agent/outcome을 통해 성공, 설정 필요, 위험 차단, 실패 또는 비관련 결과를 보고할 수 있습니다.

설치

Agent 워크플로에 추가

무료 오픈 소스. 프로덕션 Agent에 설치하기 전에 보고서를 검토하세요.

성장 루프

공유 키트

X

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
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 증거를 표시합니다.

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

작성자

D

Deupaxx

@deupaxx

플랫폼 적합도

상태 신호

GitHub 스타
28
품질 점수
33/100
최근 GitHub 푸시
2026년 8월 20일
프레임워크 힌트
알 수 없음
OpenAgentSkill 조회수
10
설치 명령 복사
0
외부 클릭
0

커뮤니티 신호

이 스킬이 Agent 워크플로에 유용한지 알려 주세요. 집계된 피드백은 시간이 지날수록 순위를 개선합니다.

신뢰와 안전

샌드박스 전용

64
  • GitHub 채택도GitHub 스타 28확인
  • 스타/포크 활동스타 28, 포크 5; 현재 메타데이터에서 이슈 활동을 확인할 수 없습니다확인
  • 최근 유지보수마지막 푸시 후 2일통과
  • 라이선스 명확성MIT통과
  • README/SKILL.md 완성도메타데이터에 충분한 사용 및 워크플로 맥락이 포함되어 있습니다통과
  • 의존성/런타임 위험공개 메타데이터에 주요 의존성 위험 힌트가 없습니다통과