Навыки 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-агентов

Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.

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 • 26.09.2026 Открыть версионный отчет

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.