📦

megacave

Name: megacave
Author: juliusbrussee

Inhaltsrevision r1 Sicher 📁 Dateisystemzugriff⚙️ Externe Befehle

Write Concise Technical Replies in Classical Chinese

Verbose technical replies can slow reading for people comfortable with Classical Chinese. Megacave applies concise Classical Chinese phrasing while preserving technical details and clear safety explanations.

Unterstützt: Claude Codex Code(CC)

🥉 77 Bronze

Maintain this Skill? Claim it 🥉 77 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage

Review the Skillstore skill "megacave" from https://skillstore.io/skills/juliusbrussee-megacave.md and its manifest at https://skillstore.io/api/skills/juliusbrussee-megacave/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/juliusbrussee-megacave.md Signiertes manifest GET /api/skills/juliusbrussee-megacave/manifest Signiertes lockfile GET /api/skills/juliusbrussee-megacave/lockfile

Testen

„megacave“ wird verwendet. Explain connection pooling in megacave mode.

Erwartetes Ergebnis:

池蓄已開之連，不逐請而新開，省握手之費。

„megacave“ wird verwendet. Explain repeated rendering caused by new object references and mention useMemo.

Erwartetes Ergebnis:

每繪新生對象參照，故重繪；以 useMemo 包之則免。

„megacave“ wird verwendet. In megacave mode, explain the next step before deleting a database permanently.

Erwartetes Ergebnis:

Deleting this database is irreversible. Confirm the exact database and verify a usable backup before proceeding.

Sicherheitsaudit

Sicher

v1 • 3.10.2026 Versionsbericht öffnen

All six static findings are false positives: a relative documentation link and Markdown inline formatting do not execute commands or access files. No evidence found of prompt injection, credential access, or data exfiltration in the two reviewed files. The skill defines an explicit response style with safety and irreversible-action exceptions.

Gescannte Dateien

Analysierte Zeilen

Prüfelemente

Falschmeldungen ignoriert

Risikofaktoren

📁 Dateisystemzugriff (1)

README.md:7

⚙️ Externe Befehle (5)

SKILL.md:18 SKILL.md:31 SKILL.md:42 SKILL.md:47 SKILL.md:59

Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.

Geprüft von: codex

Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen

Berichtslink kopieren

https://skillstore.io/skills/juliusbrussee-megacave/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/juliusbrussee-megacave/security.svg)](https://skillstore.io/skills/juliusbrussee-megacave?utm_source=security_passport_badge)

HTML-Badge

<a href="https://skillstore.io/skills/juliusbrussee-megacave?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/juliusbrussee-megacave/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Einbettungskarte

<iframe src="https://skillstore.io/embed/skills/juliusbrussee-megacave.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

juliusbrussee. (2026). megacave security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/juliusbrussee-megacave/audits/1

BibTeX-Zitat

@techreport{juliusbrussee-juliusbrussee-megacave-2026,
  author = {juliusbrussee},
  title = {megacave security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/juliusbrussee-megacave/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "megacave security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "juliusbrussee"
date-released: "2026-10-03"
url: "https://skillstore.io/skills/juliusbrussee-megacave/audits/1"
identifiers:
  - type: other
    value: "skillstore:juliusbrussee-megacave:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel

Architektur

Wartbarkeit

Inhalt

Gemeinschaft

Spezifikationskonformität

Was Sie erstellen können

Read compact debugging explanations

Receive concise Classical Chinese explanations while keeping API names, errors, and numeric details unchanged.

Reduce narration during tool workflows

Keep tool-run updates short while retaining clear warnings and confirmation requests for irreversible actions.

Compare technical writing styles

Explore Classical Chinese phrasing for technical concepts without translating identifiers or changing saved documents.

Diese Prompts ausprobieren

Explain a simple concept

/megacave Explain why a connection pool reuses open connections.

Explain a rendering issue

/megacave Explain why new object references can cause repeated rendering and when useMemo can help. Keep identifiers unchanged.

Summarize supplied diagnostics

/megacave Summarize these diagnostics: [paste diagnostics]. Preserve errors, paths, numbers, units, and negations. Use plain language for ambiguous clauses.

Separate chat style from deliverables

/megacave Review this proposed change: [paste change]. Keep chat concise, write persisted artifacts normally, and explain security concerns fully before irreversible actions.

Bewährte Praktiken

Activate the style explicitly and request normal mode when readability suffers.
Check that identifiers, negations, numbers, and units remain unchanged.
Keep security warnings, irreversible-action confirmations, and persisted artifacts in clear, ordinary language.

Vermeiden

Treating shorter displayed replies as guaranteed token or cost savings.
Translating API names, commands, paths, or errors to match the Classical Chinese style.
Compressing ambiguous instructions, security warnings, or saved documents into terse Classical Chinese.

Häufig gestellte Fragen

How do I activate megacave?

Use /megacave in Claude Code. The README also lists /caveman wenyan as an alias; availability depends on the host integration.

How do I stop the style?

Say stop caveman or normal mode. The instructions otherwise keep the style active for the session.

Does it reduce token costs?

No reliable savings are guaranteed. The README describes one small measurement and explicitly distinguishes shorter visible text from token reductions.

Will technical identifiers be translated?

No. The instructions preserve code, commands, paths, API names, errors, numbers, units, and negations.

Does it change saved documents or code?

The instructions exempt persisted artifacts from the style, including code, comments, commits, documentation, and messages. They name caveman-compress as an exception.

What happens when brevity makes a reply unclear?

Ambiguous clauses use plain Chinese. Confusion, security warnings, and irreversible-action confirmation use full sentences in plain Chinese or the user language.