Agent skill · Security

evidence-logging

Use this skill as foundation for all evidence-based review workflows. Use when conducting any review that needs evidence trails, creating audit documentation, ensuring reproducibility of analyses. Do not use when quick informal checks without documentation needs. DO NOT use when: structured output is the focus - use structured-output.'

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill evidence-logging-athola-claude-night-market --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Requires: []
Path: skills/analysis/evidence-logging-athola-claude-night-market/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Table of Contents - [When to Use](#when-to-use) - [Activation Patterns](#activation-patterns) - [Required TodoWrite Items](#required-todowrite-items) - [Step 1: Initialize Log (`evidence-logging:log-initialized`)](#step-1:-initialize-log-(evidence-logging:log-initialized)) - [Step 2: Capture Commands (`evidence-logging:commands-captured`)](#step-2:-capture-commands-(evidence-logging:commands-captured)) - [Step 3: Record Citations (`evidence-logging:citations-recorded`)](#step-3:-record-citations-(evidence-logging:citations-recorded)) - [Step 4: Index Artifacts (`evidence-logging:artifacts-indexed`)](#step-4:-index-artifacts-(evidence-logging:artifacts-indexed)) - [Evidence Reference Format](#evidence-reference-format) - [Exit Criteria](#exit-criteria) # Evidence Logging ## When To Use - During any review or analysis workflow to capture reproducible evidence. - When findings must be traceable to specific commands, outputs, or sources. - Before finalizing recommendations that stakeholders will act upon. ## When NOT To Use - Quick informal checks without documentation needs - Structured output is the focus - use structured-output ## Activation Patterns **Trigger Keywords**: evidenc

What's inside
Steps it walks through
  1. Table of Contents
  2. When To Use
  3. When NOT To Use
  4. Activation Patterns
  5. Required TodoWrite Items
  6. Step 1: Initialize Log (evidence-logging:log-initialized)
  7. Step 2: Capture Commands (evidence-logging:commands-captured)
  8. Step 3: Record Citations (evidence-logging:citations-recorded)
  9. Step 4: Index Artifacts (evidence-logging:artifacts-indexed)
  10. Evidence Reference Format
  11. Exit Criteria
  12. Supporting Modules
  13. Troubleshooting
  14. Common Issues
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the evidence-logging skill do?

Use this skill as foundation for all evidence-based review workflows. Use when conducting any review that needs evidence trails, creating audit documentation, ensuring reproducibility of analyses. Do not use when quick informal checks without documentation needs. DO NOT use when: structured output is the focus - use structured-output.'

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill evidence-logging-athola-claude-night-market --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going