📦

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.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

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

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: 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.