Log access to Claude configuration artefacts (CLAUDE.md, rules, skills, commands, agents). This skill should be invoked automatically after reading configuration files to track usage.
64
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/artefact-logger/SKILL.mdLog access to Claude configuration artefacts for usage tracking.
Invoke this skill after reading:
CLAUDE.md files.claude/rules/** files.claude/skills/** files.skills/commands/** files.claude/agents/** files (custom agents only, not internal Task tool agents)Run the script with required arguments:
.claude/skills/artefact-logger/scripts/log-artefact.sh "<name>" "<path>" "<type>"| Argument | Description | Valid Values |
|---|---|---|
name | Filename or skill/agent name | Any string |
path | Relative path or identifier | Any path string |
type | Artefact type | claude_md, rule, skill, command, agent |
# Log CLAUDE.md access
.claude/skills/artefact-logger/scripts/log-artefact.sh "CLAUDE.md" "CLAUDE.md" "claude_md"
# Log rule access
.claude/skills/artefact-logger/scripts/log-artefact.sh "standard-changelog.md" ".claude/rules/packmind/standard-changelog.md" "rule"
# Log skill invocation
.claude/skills/artefact-logger/scripts/log-artefact.sh "signal-capture" "signal-capture" "skill".claude/agents/**.claude/artefacts.yaml if missinge198635
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.