📦

megacave

Name: megacave
Author: juliusbrussee

Revisión del contenido r1 Seguro 📁 Acceso al sistema de archivos⚙️ Comandos externos

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.

Compatible con: Claude Codex Code(CC)

🥉 77 Bronce

Maintain this Skill? Claim it 🥉 77 Bronce

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente

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.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Detalle Markdown GET /skills/juliusbrussee-megacave.md Manifest firmado GET /api/skills/juliusbrussee-megacave/manifest Lockfile firmado GET /api/skills/juliusbrussee-megacave/lockfile

Pruébalo

Usando "megacave". Explain connection pooling in megacave mode.

Resultado esperado:

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

Usando "megacave". Explain repeated rendering caused by new object references and mention useMemo.

Resultado esperado:

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

Usando "megacave". In megacave mode, explain the next step before deleting a database permanently.

Resultado esperado:

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

Auditoría de seguridad

Seguro

v1 • 3/10/2026 Abrir el informe versionado

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.

Archivos escaneados

Líneas analizadas

Elementos de revisión

Falsos positivos ignorados

Factores de riesgo

📁 Acceso al sistema de archivos (1)

README.md:7

⚙️ Comandos externos (5)

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

La auditoría estática y semántica completada más reciente no detectó hallazgos de seguridad confirmados. Esto no demuestra que el skill no tenga efectos secundarios.

Auditado por: codex

Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado

Copiar enlace del informe

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

Insignia Markdown

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

Insignia HTML

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

Tarjeta para insertar

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

Citas académicas (APA · BibTeX · CFF)

Cita APA

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

Cita BibTeX

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

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio

Arquitectura

Mantenibilidad

Contenido

Comunidad

Cumplimiento de la especificación

Lo que puedes crear

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.

Prueba estos prompts

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.

Mejores prácticas

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.

Evitar

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.

Preguntas frecuentes

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.