Skills claude-reflect

📦

claude-reflect

Name: claude-reflect
Author: BayramAnnakov

Content revision r2 Safe 📁 Filesystem access⚙️ External commands🌐 Network access

Capture corrections and update your CLAUDE.md memory

Claude Code forgets your corrections between sessions, so you repeat the same guidance again and again. claude-reflect captures those corrections automatically and lets you review and apply them to your CLAUDE.md memory files with one command.

Supports: Claude Codex Code(CC)

🥉 79 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 "claude-reflect" from https://skillstore.io/skills/bayramannakov-claude-reflect.md and its manifest at https://skillstore.io/api/skills/bayramannakov-claude-reflect/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.

Markdown detail GET /skills/bayramannakov-claude-reflect.md Signed manifest GET /api/skills/bayramannakov-claude-reflect/manifest Signed lockfile GET /api/skills/bayramannakov-claude-reflect/lockfile

Test it

Using "claude-reflect". no, use gpt-5.1 not gpt-5 for reasoning tasks

Expected outcome:

The correction is captured to the local queue. On the next /reflect run, it is offered as the learning 'Use gpt-5.1 for reasoning tasks' with a suggested global scope, and you approve before it is written.

Using "claude-reflect". /reflect

Expected outcome:

One learning is found in the queue. You are shown the learning text, its suggested memory target, and a yes or no prompt to apply it.

Security Audit

Safe

v10 • 7/21/2026 Open versioned report

claude-reflect is a documentation-only Claude Code plugin corpus (8 Markdown/text files, no executable scripts in scope). All 91 static findings were adjudicated as false positives: the `~/.claude/*` references are the plugin's own documented memory-hierarchy and queue storage, the two CRITICAL `rm -rf` hits are user-facing cache-clearing instructions scoped to a specific named plugin-cache subdirectory in the README troubleshooting section, the 'backtick execution' hits are Markdown inline-code/code-fence syntax, and the hardcoded URLs point to the project's own public repository. No prompt-injection, data-exfiltration, or business-logic-abuse intent was found.

Files scanned

1,260

Lines analyzed

Review items

False positives ignored

Risk Factors

📁 Filesystem access (50)

⚙️ External commands (24)

🌐 Network access (8)

DISTRIBUTION.md:88 DISTRIBUTION.md:105 DISTRIBUTION.md:137 DISTRIBUTION.md:139 DISTRIBUTION.md:184 DISTRIBUTION.md:215 DISTRIBUTION.md:226 DISTRIBUTION.md:242

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: claude View Audit History →

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

Copy report link

https://skillstore.io/skills/bayramannakov-claude-reflect/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

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

HTML badge

<a href="https://skillstore.io/skills/bayramannakov-claude-reflect?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bayramannakov-claude-reflect/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/bayramannakov-claude-reflect.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

BayramAnnakov. (2026). claude-reflect security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bayramannakov-claude-reflect/audits/10

BibTeX citation

@techreport{bayramannakov-bayramannakov-claude-reflect-2026,
  author = {BayramAnnakov},
  title = {claude-reflect security audit report (audit version 10)},
  institution = {Skillstore},
  year = {2026},
  number = {10},
  url = {https://skillstore.io/skills/bayramannakov-claude-reflect/audits/10},
  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: "claude-reflect security audit report (audit version 10)"
version: "unspecified"
type: report
authors:
  - name: "BayramAnnakov"
date-released: "2026-07-21"
url: "https://skillstore.io/skills/bayramannakov-claude-reflect/audits/10"
identifiers:
  - type: other
    value: "skillstore:bayramannakov-claude-reflect:audit:10"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Stop repeating the same corrections

A developer who keeps telling Claude Code the same project conventions can capture those corrections once and apply them to the project CLAUDE.md file.

Keep team conventions in sync

A team lead can review queued learnings before they are written, so shared CLAUDE.md files stay accurate and reviewed.

Recover missed learnings from past work

A user returning to a project can scan past sessions to find corrections that were never saved and add them to memory.

Try These Prompts

Review queued learnings

Run /reflect and show me the learnings that are queued before applying any of them.

Preview changes safely

Run /reflect --dry-run so I can see what would change in my CLAUDE.md files without writing anything.

Scan history for missed learnings

Run /reflect --scan-history and list corrections from past sessions that were never saved.

Discover reusable skills

Run /reflect-skills over the last 30 days and propose skill candidates from repeating patterns, but do not create any files yet.

Best Practices

Review learnings with /reflect --dry-run before applying them so you can see the exact changes.
Run /reflect at natural stopping points, such as after finishing a feature or before context compaction.
Choose the narrowest memory target that fits, using project files for project rules and global files only for broad patterns.

Avoid

Do not apply every queued learning without reading it, because low-value corrections can clutter your memory files.
Do not store secrets, tokens, or personal data in captured learnings, since memory files persist across sessions.
Do not rely on capture alone to remember important rules; run /reflect so learnings are actually written.