Skills megacave
πŸ“¦

megacave

Content revision r1 Safe πŸ“ Filesystem accessβš™οΈ External commands

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.

Supports: Claude Codex Code(CC)
πŸ₯‰ 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
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.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

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

Expected outcome:

ζ± θ“„ε·²ι–‹δΉ‹ι€£οΌŒδΈι€θ«‹θ€Œζ–°ι–‹οΌŒηœζ‘ζ‰‹δΉ‹θ²»γ€‚

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

Expected outcome:

每ηΉͺζ–°η”Ÿε°θ±‘εƒη…§οΌŒζ•…ι‡ηΉͺοΌ›δ»₯ useMemo εŒ…δΉ‹ε‰‡ε…γ€‚

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

Expected outcome:

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

Security Audit

Safe
v1 β€’ 10/3/2026 Open versioned report

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.

2
Files scanned
76
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

πŸ“ Filesystem access (1)
βš™οΈ External commands (5)
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

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>

Embed card

<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>
Academic citations (APA Β· BibTeX Β· CFF)

APA citation

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

BibTeX citation

@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

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

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.

Try These 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.

Best Practices

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

Avoid

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

Frequently Asked Questions

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.

Developer Details

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

38c2032d9c994f040745f35e98d3f24904b417cc

Maintenance freshness

10/3/2026

Usage

0 downloads Β· 0 views

File structure

πŸ“„ README.md

πŸ“„ SKILL.md

More from juliusbrussee

View all
View all