スキル cc-best-practices

📦

cc-best-practices

Name: cc-best-practices
Author: dboeckli

コンテンツリビジョン r1 中リスク ⚙️ 外部コマンド📁 ファイルシステムへのアクセス🌐 ネットワークアクセス

Improve Claude Code Workflows

Unclear prompts and crowded sessions reduce coding quality. This skill provides practical workflows for planning, verification, context control, automation, and independent review.

対応: Claude Codex Code(CC)

📊 71 十分

Maintain this Skill? Claim it 📊 71 十分

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

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

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

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

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

Markdown詳細 GET /skills/dboeckli-cc-best-practices.md 署名済み manifest GET /api/skills/dboeckli-cc-best-practices/manifest 署名済み lockfile GET /api/skills/dboeckli-cc-best-practices/lockfile

テストする

「cc-best-practices」を使用しています。 Help me ask Claude to fix an intermittent login failure.

期待される結果:

Investigate login failures after session timeout. Inspect authentication refresh logic, add a reproducing test, implement the fix, and report test evidence.

「cc-best-practices」を使用しています。 My session is long, and Claude repeats the same mistake.

期待される結果:

Record the missing constraint and any useful evidence.
Clear the unrelated conversation context.
Start again with the constraint, affected files, expected behavior, and a verification command.

「cc-best-practices」を使用しています。 How should my team review a large refactor?

期待される結果:

Use one session to implement the approved plan and another fresh session to inspect the diff, edge cases, and verification results.

セキュリティ監査

中リスク

v1 • 2026/9/26 バージョン別レポートを開く

All 43 static alerts are false positives: the script uses fixed local validation commands, while the documentation alerts identify Markdown or benign examples. Two contextual risks remain because examples recommend sending logs to Claude and enabling broad unattended execution without adequate cautions.

スキャンされたファイル

371

解析済み行数

レビュー項目

誤検知を無視

確認済みのセキュリティ上の懸念 (2)

中

SKILL.md:142-145

Potential Sensitive Log Disclosure

The skill recommends piping an error log to Claude without advising users to review or redact secrets and personal data first.

The explicit log piping example can transmit complete log contents to an external model service, and no nearby redaction warning is present.

中

SKILL.md:229-249 references/commands.md:31-38

Overbroad Unattended Automation Guidance

Examples allow editing and wildcard git commits, then recommend auto permission mode without requiring review before persistent changes.

The documented commands explicitly grant broad edit and git commit access and promote uninterrupted auto mode, creating clear unintended-change risk.

リスク要因

⚙️ 外部コマンド (38)

📁 ファイルシステムへのアクセス (2)

scripts/validate-claude-md.sh:10 scripts/validate-claude-md.sh:8

🌐 ネットワークアクセス (1)

SKILL.md:10

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/dboeckli-cc-best-practices/security.svg)](https://skillstore.io/skills/dboeckli-cc-best-practices?utm_source=security_passport_badge)

HTMLバッジ

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

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/dboeckli-cc-best-practices.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形式の引用

dboeckli. (2026). cc-best-practices security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1

BibTeX形式の引用

@techreport{dboeckli-dboeckli-cc-best-practices-2026,
  author = {dboeckli},
  title = {cc-best-practices security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/dboeckli-cc-best-practices/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: "cc-best-practices security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "dboeckli"
date-released: "2026-09-26"
url: "https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1"
identifiers:
  - type: other
    value: "skillstore:dboeckli-cc-best-practices:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Plan a Complex Change

Structure exploration, planning, implementation, and verification before editing several related files.

Standardize Team Instructions

Create a concise CLAUDE.md that records project-specific commands, architecture, testing rules, and repository conventions.

Scale Repetitive Analysis

Choose subagents, non-interactive commands, or parallel worktrees while preserving focused review and verification.

これらのプロンプトを試す

Improve a Task Prompt

Rewrite my request with explicit scope, relevant files, constraints, expected behavior, and one runnable verification step.

Prepare an Implementation Plan

Explore the affected code without editing. Then produce a sequenced plan with dependencies, risks, files, and verification commands.

Recover From Repeated Errors

Identify missing context behind repeated failures. Draft a fresh prompt that states the constraint, example, scope, and acceptance test.

Design a Parallel Workflow

Design separate writer and reviewer sessions using worktrees. Define ownership, allowed tools, handoff evidence, and final integration checks.

ベストプラクティス

Provide a runnable check and request evidence from its output.
Separate exploration, planning, implementation, and independent review for complex work.
Keep persistent instructions short, project-specific, and necessary.

回避

Do not combine unrelated tasks in one crowded session.
Do not continue correcting the same failure without improving the original context.
Do not grant broad automation permissions without reviewing data exposure and persistent changes.