skill-analyzer
- 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-analyzer
description: | 读取 06 计划/skillusagelog.jsonl,分析 Skill 使用情况,输出本周总结报告。 $OBSIDIANVAULT/06 计划/skillusage_log.jsonl…
category: other
runtime: no special runtime
---
# skill-analyzer output preview
## PART A: Task fit
- Use case: | 读取 06 计划/skillusagelog.jsonl,分析 Skill 使用情况,输出本周总结报告。 $OBSIDIANVAULT/06 计划/skillusage_log.jsonl 默认分析最近 7 天。指定时间范围: 分析过去两周的 Skill 数据 python3 scripts/analyzeskillusage.py --days 7 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 “| 读取 06 计划/skillusagelog.jsonl,分析 Skill 使用情况,输出本周总结报告。 $OBSIDIANVAULT/06 计划/skillusage_log.jsonl 默认分析最近 7 天。指定时间范围: 分析过去两周的 Skill 数据 python3 scripts/analyzeskillusage.py --days 7 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-analyzer
description: | 读取 06 计划/skillusagelog.jsonl,分析 Skill 使用情况,输出本周总结报告。 $OBSIDIANVAULT/06 计划/skillusage_log.jsonl…
category: other
source: zephyrwang6/myskill
---
# skill-analyzer
## When to use
- | 读取 06 计划/skillusagelog.jsonl,分析 Skill 使用情况,输出本周总结报告。 $OBSIDIANVAULT/06 计划/skillusage_log.jsonl 默认分析最近 7 天。指定时间范围: 分析…
- 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-analyzer" {
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 使用分析
读取 06 计划/skill_usage_log.jsonl,分析 Skill 使用情况,输出本周总结报告。
日志文件位置
$OBSIDIAN_VAULT/06 计划/skill_usage_log.jsonl
使用方式
分析 Skill 使用情况
默认分析最近 7 天。指定时间范围:
分析过去两周的 Skill 数据
工作流程
Step 1:运行分析脚本
python3 scripts/analyze_skill_usage.py --days 7
指定时间范围:
python3 scripts/analyze_skill_usage.py --days 14
Step 2:输出分析报告
脚本输出原始数据后,AI 整理成以下格式的报告:
📊 Skill 使用周报(最近 7 天)
总览
- 共使用 Skill N 次,覆盖 X 个不同 Skill
- 平均满意度:X.X / 5
使用频率排行
| 排名 | Skill | 使用次数 | 平均满意度 |
|---|---|---|---|
| 1 | x-post | 8 | 4.2 |
| 2 | podcast-workflow | 5 | 4.6 |
| 3 | content-digest | 4 | 4.0 |
满意度偏低的 Skill(< 3.5 分)
| Skill | 平均满意度 | 常见问题 |
|---|---|---|
| xxx | 3.0 | 备注中反复出现"改了结尾" |
本周未使用的 Skill(有记录但本周零调用)
- skill-a
- skill-b
建议
xxx满意度持续下降,建议检查 SKILL.md 是否需要更新规则yyy两周未使用,考虑是否仍有需求zzz本周高频使用,可以考虑做自动化
Step 3:询问是否归档
要把这份报告存到 06 计划/05 周复盘/ 吗?
环境变量配置
在 ~/.env 或项目根目录的 .env 文件中配置:
OBSIDIAN_VAULT=/Users/ugreen/Documents/obsidian
Decide Fit First
Design Intent
How To Use It
Boundaries And Review