sales-copy

Prüfen · 66
Im Registry indexiert

Write sales pages, email sequences, and direct-response copy that converts through clarity and specificity rather than manipulation. Use for launches, offers, and conversion-focused email. Enforces the EW anti-AI rules, proof standards, and the writer's voice profile.

Verified installs0
Stars28
Version1.0.0
Qualität62/100 · Vielversprechend
Vertrauen66/100 · Nur Sandbox
Audit77/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 sales-copy

Wartung

Aktuell

2 Tage seit dem letzten Push

Risiko

Prüfung nötig

The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.

GitHub-Qualität

28

62/100 Qualität · 74/100 Vertrauen

Abdeckungs-Tags

RechercheRecherche-Agentsagent-skill

Review-Notizen

The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse. · Low GitHub adoption signal

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
62

Useful candidate, but compare it with alternatives before adopting.

Vertrauen

Nur Sandbox
66

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

Audit

Prüfung nötig
77

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

2 Tage seit dem letzten Push

Lizenz

MIT

Installieren

npx skills add Deupaxx/EveryDay-Writer --skill sales-copy

Installationssicherheit

Standard-Paket- oder Laufzeit-Installationspfad

Berechtigungsfläche

Keine Hochrisiko-Berechtigungsfläche in öffentlichen Metadaten

Agent-Ergebnisse

Noch keine Agent-Ergebnisdaten

Dokumentation

Usable metadata, review docs

Risikoübersicht

Vor Produktion prüfen

  • The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
  • Low GitHub adoption signal
  • Quality score needs review
  • GitHub adoption: 28 GitHub stars

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

  • Content automation-Workflows
  • Claude-Code-Teams
  • builders willing to evaluate younger projects
  • Summarize source material

Geeignete Agents

CodexClaude CodeCursorOpenAgentSkill CLICLI

Installationsentscheidung

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

Vertrauen und Risiko

Vertrauen
66/100
Audit
77/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 sales-copy

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.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
  • Quality score needs review

Agent-Sicherheit v2

57/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.

  • The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.

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

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 sales-copy in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20sales-copy%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/deupaxx-sales-copy/install
Install command: npx skills add Deupaxx/EveryDay-Writer --skill sales-copy
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 sales-copy for this task. Review https://www.openagentskill.com/api/skills/deupaxx-sales-copy/install, then install with: npx skills add Deupaxx/EveryDay-Writer --skill sales-copy

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

62/100

Content automation

Plattformen

Claude Code

Audit-Bericht

Prüfung nötig · 77/100

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

Audit-Bericht ansehenEval-Bericht ansehen

Agent-Entscheidungspanel

Fallback candidate for Content automation

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

62
Bereitschaft
Prototyp
Phase

Rolle im Stack

Fallback-Kandidat

Primäre Eignung

Content automation

Vertrauenslabel

Zuerst prototypisieren

Installationspfad

Befehl bereit

Verwenden wenn

  • Content automation-Workflows
  • Claude-Code-Teams
  • builders willing to evaluate younger projects

Evidenz

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

zuerst prüfen

  • Low GitHub adoption signal
  • The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.

Implementierungspfad

  1. 1Installieren Sie es in einem Sandbox-Agent und führen Sie eine Content automation-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.

66
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

2 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.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.
  • 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.

62
GitHub-Stars
28
Aktualität
vor 2 Tagen
Installationsbereit
Ja
Lizenz
MIT
Vor Installation prüfen: Low GitHub adoption signal · The SKILL.md references core dependency files (core/anti-ai-rules.md, core/ai_slop_commandments.md, core/voice-profile.md) that are not included in the skill directory itself. This is acceptable if the skill is used within the full repository, but it may hinder standalone reuse.

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: sales-copy description: | Write sales pages, email sequences, and direct-response copy that converts through clarity and specificity rather than manipulation. Use for launches, offers, and conversion-focused email. Enforces the EW anti-AI rules, proof standards, and the writer's voice profile. license: MIT metadata: version: "0.3.0" ---

# EW Skill — Sales Copy

**Dependency chain. Read these in order before writing anything:**

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; if `Completed: No`, stop and run onboarding) 4. Any `.md` files the user has dropped in `references/`

This chain applies on direct invocation (`/ew:sales-copy`) exactly as it does on dispatch through `/ew`. Direct invocation skips routing, not constraints.

---

## WHAT THIS SKILL IS FOR

Sales pages, email sequences, and direct response copy. Writing that exists to produce a measurable outcome: a purchase, a booking, a subscription, an enrollment.

Sales copy is the most honest form of writing because it can't hide its intent. It either converts or it doesn't. The number tells you. The discipline here is writing that moves people toward something they genuinely need — not manipulating them into something they don't.

Manipulation is not this skill's tool. Clarity, specificity, and legitimate persuasion are.

---

## THE STRUCTURAL SPINE: THE CUSTOMER AS PROTAGONIST

The Triad of Craft and the writing commandments converge on one insight for sales copy: the customer is the protagonist, not the product. The product is the key knowledge found at the midpoint of their journey. The copy must tell their story, not yours.

**The sales copy as hero's journey:**

**Ordinary World:** The customer's life before. The problem that exists. The pain that is real. State it more specifically than they've heard it before — this is what creates the "they understand me" moment that earns trust.

**Inciting Incident:** The moment their ordinary world is no longer acceptable. What made them start looking? What made the pain acute enough to act? Naming this is the difference between copy that resonates and copy that gets scrolled past.

**The Woods:** What they've already tried. What failed. Why the usual solutions don't work for this specific problem. This section is often skipped — it shouldn't be. Acknowledging failed attempts proves you understand the problem deeply.

**Key Knowledge:** The mechanism. Why this product/service works where others didn't. Not a feature list — the one insight about the problem that makes the solution make sense.

**New Equilibrium:** Life after. Specific. Grounded. Not "transform your business" — "you stop writing from scratch every time and start from a brief that already has the argument."

---

## THE OPENING

The sole purpose of the first sentence is to get the reader to read the second sentence.

The opening must do one of three things: name the reader's problem so specifically they feel seen, challenge a belief they hold, or present a specific outcome they want. No preamble. No warm-up. The reader made the decision to stay or go in the first three seconds.

**What works:**

**The problem, stated precisely:** "You've bought three copywriting courses. Your conversion rate is the same as when you started."

**The specific outcome:** "A sales page that converts at 8% when your current one converts at 1.2%."

**The challenge:** "Most sales pages fail before the reader reaches the first CTA — and it's not the CTA that's broken."

**What doesn't work:** - "Are you tired of...?" — exhausted opener, signals template - "Imagine a world where..." — futurism invitation, signals AI - "I used to struggle with this too..." — false vulnerability, signals performance - Long story openers that bury the point past the 300-word mark

---

## SPECIFICITY IS THE PROOF

In sales copy, specificity is the mechanism of trust. Every vague claim is a credibility debit. Every specific claim is a credibility credit.

**The specificity upgrade:**

❌ "This program has helped hundreds of businesses grow." ✅ "47 solo consultants used this to book their first $5,000 client within 90 days."

❌ "Our clients see amazing results." ✅ "Amara increased her newsletter conversion rate from 1.8% to 6.3% in 60 days using only the cold traffic sequence in Module 3."

The number, the name, the timeframe, the specific mechanism — these are what make claims land. Without them, you're asking the reader to trust you on faith. Most won't.

**Name the mechanism:** Don't just say the product works — explain briefly *why* it works. The mechanism is what separates a claim from an argument. ❌ "This headline formula gets clicks." ✅ "This headline formula works because it triggers pattern interruption — the reader's brain stops scanning when it encounters something that doesn't fit the template it was expecting."

---

## OBJECTION ARCHITECTURE

Every unconverted reader is a reader with an unaddressed objection. Your copy must find and answer the three to five objections that kill the most conversions — before the reader has to ask.

**The main objections in most sales situations:** 1. "Is this for someone like me?" — Too broad, won't work in my situation 2. "Will this actually work?" — Skepticism about the mechanism or promise 3. "Can I trust you?" — Credibility gap, insufficient proof 4. "Is it worth the cost?" — ROI isn't clear 5. "Is now the right time?" — Urgency isn't real

**Address each with specifics, not reassurance.** Reassurance ("We're confident you'll love it!") doesn't address objections — it papers over them. The reader can feel the difference.

Objection: "I've tried things like this before and they didn't work." Reassurance: "We think you'll be pleasantly surprised!" Address: "Most [category] courses teach the framework without the implementation step. This one starts at implementation. Here's what that looks like on day one:"

---

## PROOF ARCHITECTURE

Proof is not a section at the bottom of the page. It is distributed throughout the copy, placed nearest to the claim it supports.

**Types of proof, in descending order of power:** 1. **Specific named results with numbers and timeframes** — the most trusted form 2. **Named testimonials with specific outcomes** — not "John changed my business," but "John's launch converted at 4.2% where his previous launch was at 0.9%" 3. **Your own demonstrated expertise** — specific, named, verifiable 4. **Mechanism explanation** — showing you understand *why* it works 5. **Social proof (numbers, logos, media)** — useful but weakest without specifics

**Never use:** - Anonymous testimonials - Testimonials with only first name and last initial - Testimonials that only praise the person, not the result - Claims you can't substantiate

---

## EMAIL SEQUENCES

An email sequence is a conversation across time. Each email must earn the right to send the next one.

**The first email's job:** Establish why the reader is here and what they'll get. Not a full pitch — a clear reason to open the next one.

**Middle emails:** Deepen the argument. Each email handles one aspect of the case for action. One idea per email. Every email ends with a forward pointer that makes the next one feel necessary.

**The sales email:** After the relationship and the argument are built. The offer, stated clearly and honestly. The mechanism, the proof, the CTA. One CTA. No hedge. No apology for selling.

**Subject lines:** Write for the opened inbox of someone who doesn't know what's inside. The subject line earns the open; the first line earns the read.

---

## WHAT THIS SKILL DOES NOT DO

This skill does not generate false urgency ("only 3 spots left" when there are unlimited spots), manufacture scarcity, or write copy that misrepresents what the product does. These techniques work once and destroy trust permanently.

If the offer is good, honesty converts. If the offer requires manipulation to convert, the offer is the problem — not the copy.

---

## POST-GENERATION REVIEW

After producing any draft, stop. Re-read `core/anti-ai-rules.md` Sections 1–7 with the draft in front of you. Go line by line through the pre-publish checklist in Section 7. Fix every failure before presenting the output.

Sales copy that reads as AI-generated destroys the trust it needs to convert. The review pass is not quality control — it is the product.

## PRE-LAUNCH CHECKLIST

- [ ] Does the opening name the reader's specific problem or desired outcome in the first 3 sentences? - [ ] Is the customer the protagonist — or is the product? - [ ] Is every claim backed by a specific number, name, or mechanism? - [ ] Are testimonials named and outcome-specific? - [ ] Are the top 5 objections addressed with specifics, not reassurance? - [ ] Is the mechanism explained — not just claimed? - [ ] Is there one clear CTA per section? - [ ] Have you run Sections 1–7 of `core/anti-ai-rules.md`? - [ ] Is all urgency or scarcity real — not manufactured? - [ ] Does the copy end having proved something, or just asserted it?

Technische Details

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

Entscheidungsübersicht

Fallback-Kandidat

62
Bereit
Prototyp
Phase

recent repository activity

Audit

Installationsprüfung

Installations- und Adoptionsprüfung

77
Prüfung nötig
Sicherheit
81/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 sales-copy, bereit für einen manuellen X-Post.

Kuratorenhinweis
sales-copy: Write sales pages, email sequences, and direct-response copy that converts through clarity an...

28 stars

https://www.openagentskill.com/skills/deupaxx-sales-copy?ref=x
X-Entwurf öffnen
Optionale Antwort mit Installationsbefehl
Listing + install path for sales-copy:
https://www.openagentskill.com/skills/deupaxx-sales-copy?ref=x

Install: npx skills add Deupaxx/EveryDay-Writer --skill sales-copy
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-sales-copy?metric=listed&label=Listed)](https://www.openagentskill.com/skills/deupaxx-sales-copy)
[![OpenAgentSkill Trust](https://www.openagentskill.com/api/badge/deupaxx-sales-copy?metric=trust&label=Trust)](https://www.openagentskill.com/skills/deupaxx-sales-copy)
[![OpenAgentSkill Audit](https://www.openagentskill.com/api/badge/deupaxx-sales-copy?metric=audit&label=Audit)](https://www.openagentskill.com/skills/deupaxx-sales-copy/audit)
[![Agent Proven](https://www.openagentskill.com/api/badge/deupaxx-sales-copy?metric=proven&label=Agent%20Proven)](https://www.openagentskill.com/skills/deupaxx-sales-copy)

Autor

D

Deupaxx

@deupaxx

Plattform-Fit

Gesundheitssignale

GitHub-Stars
28
Qualitätswert
34/100
Letzter GitHub-Push
20. Aug. 2026
Framework-Hinweise
Unbekannt
OpenAgentSkill-Aufrufe
3
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

66
  • 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 Wartung2 Tage seit dem letzten PushBestanden
  • LizenzklarheitMITBestanden
  • README/SKILL.md-VollständigkeitÖffentliche Metadaten benötigen mehr README/SKILL.md-KontextInfo
  • Abhängigkeits-/LaufzeitrisikoKeine wesentlichen Abhängigkeitsrisikohinweise in öffentlichen MetadatenBestanden