npx skills add smithery/scooter-lacroix --skill observe-before-editing
parcadei/continuous-claude-v3
observe-before-editing
Observe Before Editing
Installation
npx skills add parcadei/continuous-claude-v3 --skill observe-before-editing
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo …
10.2K installsUse for anything related to EAS Observe — adding `expo-observe` to an Expo project (AppMetricsR…
6.4K installsMonitors task execution for skill improvement opportunities. Use during ANY multi-step task, ag…
6.2K installsAnalyze production Agentforce agent behavior using session traces and Data Cloud, and manage Ag…
5.3K installsObserve and troubleshoot WhatsApp in Kapso: search Logs across API, Meta webhook, workflow, and…
2.7K installsTechniques for planning user research and synthesising it into grounded, confidence-rated findi…
1.8K installsAlso in this package
Other skills from parcadei/continuous-claude-v3 · top by installs.
npx skills add parcadei/continuous-claude-v3
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,067 B -
docs
SUMMARY.md49 B
History
- First seen on skills.sh
- First recorded snapshot · 476 installs
SKILL.md
Observe Before Editing
Before editing code to fix a bug, confirm what the system actually produced.
Pattern
Outputs don't lie. Code might. Check outputs first.
DO
- Check if expected directories exist:
ls -la .claude/cache/ - Check if expected files were created:
ls -la .claude/cache/learnings/ - Check logs for errors:
tail .claude/cache/*.log - Run the failing command manually to see actual error
- Only then edit code
DON'T
- Assume "hook didn't run" without checking outputs
- Edit code based on what you think should happen
- Confuse global vs project paths (check both:
.claude/and~/.claude/)
Source Sessions
- a541f08a: Token limit error was invisible until manual run revealed it
- 6a9f2d7a: Looked in wrong cache path (
~/.claude/vs.claude/), assumed hook failure - a8bd5cea: Confirmed hook worked by finding output files in project cache
- 1c21e6c8: Verified Artifact Index indexing by checking DB file exists