技能 megacave

📦

megacave

Name: megacave
Author: juliusbrussee

內容修訂 r1 安全 📁 檔案系統存取⚙️ 外部命令

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.

支援: Claude Codex Code(CC)

🥉 77 銅級

Maintain this Skill? Claim it 🥉 77 銅級

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

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.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/juliusbrussee-megacave.md 已簽名 manifest GET /api/skills/juliusbrussee-megacave/manifest 已簽名 lockfile GET /api/skills/juliusbrussee-megacave/lockfile

測試它

正在使用「megacave」。 Explain connection pooling in megacave mode.

預期結果:

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

正在使用「megacave」。 Explain repeated rendering caused by new object references and mention useMemo.

預期結果:

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

正在使用「megacave」。 In megacave mode, explain the next step before deleting a database permanently.

預期結果:

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

安全審計

安全

v1 • 2026/10/3 開啟版本化報告

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.

已掃描檔案

分析行數

複核項目

已忽略的誤報

風險因素

📁 檔案系統存取 (1)

README.md:7

⚙️ 外部命令 (5)

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

最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。

審計單位: codex

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

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

Markdown 徽章

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

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>

嵌入卡片

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

學術引用 (APA · BibTeX · CFF)

APA 引用

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

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"

Skillstore 評分

評分依據證據置信度: 中

架構

可維護性

內容

社群

規範符合度

你可以打造什麼

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.

試試這些提示

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.

最佳實務

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.

避免

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.

常見問題

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.