skill-logger
- Repo stars 304
- Author updated Live
- Author repo myskill
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @zephyrwang6 · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Env read
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-logger
description: | 每次使用完某个 Skill 后，调用本 Skill 记录一条使用日志。日志追加到 06 计划/skillusagelog.jsonl。 $OBSIDIANVAULT/06 计划/skill…
category: other
runtime: no special runtime
---
# skill-logger output preview
## PART A: Task fit
- Use case: | 每次使用完某个 Skill 后，调用本 Skill 记录一条使用日志。日志追加到 06 计划/skillusagelog.jsonl。 $OBSIDIANVAULT/06 计划/skillusage_log.jsonl 记录这次使用：x-post，场景是把播客笔记改成即刻动态，满意度 4 分，结尾不够有力手动改了 直接说"记录一下"，AI 会依次询问： runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “日志文件位置 / 使用方式 / 工作流程” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| 每次使用完某个 Skill 后，调用本 Skill 记录一条使用日志。日志追加到 06 计划/skillusagelog.jsonl。 $OBSIDIANVAULT/06 计划/skillusage_log.jsonl 记录这次使用：x-post，场景是把播客笔记改成即刻动态，满意度 4 分，结尾不够有力手动改了 直接说"记录一下"，AI 会依次询问： runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “日志文件位置 / 使用方式 / 工作流程” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, read environment variables, write/modify files.
Start with a small task and check whether the result follows “日志文件位置 / 使用方式 / 工作流程”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skill-logger
description: | 每次使用完某个 Skill 后，调用本 Skill 记录一条使用日志。日志追加到 06 计划/skillusagelog.jsonl。 $OBSIDIANVAULT/06 计划/skill…
category: other
source: zephyrwang6/myskill
---
# skill-logger
## When to use
- | 每次使用完某个 Skill 后，调用本 Skill 记录一条使用日志。日志追加到 06 计划/skillusagelog.jsonl。 $OBSIDIANVAULT/06 计划/skillusage_log.jsonl 记录这次使用…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “日志文件位置 / 使用方式 / 工作流程” and keep inference separate from source facts.
- read files, read environment variables, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skill-logger" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 日志文件位置 / 使用方式 / 工作流程
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, read environment variables, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Skill 使用日志记录
每次使用完某个 Skill 后，调用本 Skill 记录一条使用日志。日志追加到 06 计划/skill_usage_log.jsonl。
日志文件位置
$OBSIDIAN_VAULT/06 计划/skill_usage_log.jsonlOBSIDIAN_VAULT 环境变量需在 .env 中配置（见下方）。
使用方式
方式一：用完 Skill 后手动触发
记录这次使用：x-post，场景是把播客笔记改成即刻动态，满意度 4 分，结尾不够有力手动改了方式二：让 AI 引导填写
直接说"记录一下"，AI 会依次询问：
- 用了哪个 Skill？
- 使用场景是什么？
- 满意度（1-5 分）？
- 备注（可选）？
工作流程
Step 1：收集信息
如果用户没有提供完整信息，逐项询问：
- skill：Skill 名称（如
x-post） - scene：这次用它做了什么（一句话描述）
- satisfaction：满意度 1-5 分（1=很差，3=一般，5=完美）
- note：备注，比如哪里不满意、手动改了什么（可为空）
Step 2：运行追加脚本
python3 scripts/log_skill_usage.py \
--skill "x-post" \
--scene "把播客笔记改成即刻动态" \
--satisfaction 4 \
--note "结尾不够有力，手动改了"Step 3：确认写入
脚本输出追加成功后，向用户确认：
✅ 已记录：x-post（满意度 4/5）
场景：把播客笔记改成即刻动态
备注：结尾不够有力，手动改了日志格式
每条记录是一行 JSON：
{"date": "2026-03-24", "weekday": "周二", "week": "W13", "skill": "x-post", "scene": "把播客笔记改成即刻动态", "satisfaction": 4, "note": "结尾不够有力，手动改了"}环境变量配置
在 ~/.env 或项目根目录的 .env 文件中配置：
# Skill 日志文件所在的 Obsidian vault 路径
OBSIDIAN_VAULT=/Users/ugreen/Documents/obsidian脚本通过 os.environ['OBSIDIAN_VAULT'] 读取，不要把路径硬编码进脚本。
Decide Fit First
Design Intent
How To Use It
Boundaries And Review