skill-lacerbi-dotclaude-files · by Install
$ agentstack add skill-lacerbi-dotclaude-files ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-lacerbi-dotclaude-files) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Task
$ARGUMENTS
Your Task
Identify the essential context files someone needs to read before starting this task — the files that rebuild the broader understanding an agent needs to avoid tunnel vision.
What This Is For
A fresh agent is about to work on this task with a clean context window. It will naturally discover specific implementation files as it works. Your job is different: identify the 3–6 files that provide the surrounding context — the big picture that prevents the agent from being over-focused on the immediate task and making mistakes from ignorance.
What to Include
- The task/plan file if one exists (e.g.,
PLAN-foo.md) - Core project docs: Architecture files, design docs, devlogs, or READMEs that explain why things are the way they are — if they are useful to understand the broader context
- Key conventions or patterns: Files that show how similar work was done, or that establish standards the task must follow
- Critical implicit context: Things that someone familiar with the project would know but a fresh agent won't
What NOT to Include
- Files the agent will find on its own through normal exploration
- Every file tangentially related to the task
- CLAUDE.md/AGENTS.md (loaded automatically)
- Long lists of implementation files — if you're listing more than ~6 files, you're being too granular
Process
- Understand the task scope
- Explore the project for broader context docs (architecture, design, devlogs, guides)
- Select the smallest set of files that gives a fresh agent the big picture
Output Format
Output a short list with brief explanations:
path/to/file - why it matters for context
path/to/other - why it matters for contextAim for ~6 files (3–6 typical; a few extra are allowed if truly important, e.g., for a fragmented knowledge base). After outputting the list, stop — do not read the files or start working.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: lacerbi
- Source: lacerbi/dotclaude
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.