Growth Log
affaan-m/ECC
Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence…
SDK 客户端日志分析 skill（带 Web 预览版）。用于本地 .clog/.xlog/文本日志的类型识别、二进制解码、TRTC/IM/TUI 客户端日志时间线解析，并提供本地日志 Web 预览服务。
No licenceAuto-check passed
Install SDK Log Analysis
$ npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install infometa/workbuddyskills sdk-log-analysis --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/experts/sdk-log-expert/skills/sdk-log-analysis .claude/skills/sdk-log-analysis && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sdk-log-analysis" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/sdk-log-expert/skills/sdk-log-analysis into .claude/skills/sdk-log-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-log-analysis", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/infometa/workbuddyskills/tree/main/experts/sdk-log-expert/skills/sdk-log-analysisType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install infometa/workbuddyskills sdk-log-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/experts/sdk-log-expert/skills/sdk-log-analysis .agents/skills/sdk-log-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sdk-log-analysis" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/sdk-log-expert/skills/sdk-log-analysis into .agents/skills/sdk-log-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-log-analysis", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install infometa/workbuddyskills sdk-log-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/experts/sdk-log-expert/skills/sdk-log-analysis .cursor/skills/sdk-log-analysis && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sdk-log-analysis" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/sdk-log-expert/skills/sdk-log-analysis into .cursor/skills/sdk-log-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-log-analysis", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/infometa/workbuddyskills.git --path experts/sdk-log-expert/skills/sdk-log-analysis--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install infometa/workbuddyskills sdk-log-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/experts/sdk-log-expert/skills/sdk-log-analysis .gemini/skills/sdk-log-analysis && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sdk-log-analysis" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/sdk-log-expert/skills/sdk-log-analysis into .gemini/skills/sdk-log-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-log-analysis", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install infometa/workbuddyskills sdk-log-analysisInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .github/skills && cp -r skills-src/experts/sdk-log-expert/skills/sdk-log-analysis .github/skills/sdk-log-analysis && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sdk-log-analysis" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/sdk-log-expert/skills/sdk-log-analysis into .github/skills/sdk-log-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-log-analysis", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install infometa/workbuddyskills sdk-log-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/infometa/workbuddyskills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/experts/sdk-log-expert/skills/sdk-log-analysis .opencode/skills/sdk-log-analysis && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sdk-log-analysis" agent skill from https://github.com/infometa/workbuddyskills/tree/main/experts/sdk-log-expert/skills/sdk-log-analysis into .opencode/skills/sdk-log-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdk-log-analysis", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sdk-log-analysis- GitHub stars
- 344
- Token cost
- ~1.4k tokens
- SKILL.md length
- 303 words
- Files
- 69 (incl. scripts, references)
- Skills in repo
- 212
- Repo updated
- First seen
- Licence
- None found
At a glance
SDK 客户端日志分析 skill（带 Web 预览版）。用于本地 .clog/.xlog/文本日志的类型识别、二进制解码、TRTC/IM/TUI 客户端日志时间线解析，并提供本地日志 Web 预览服务。
- Works in 8 steps: 本地日志入口快路径（先判类型，再分析） → 数据源 → Clog decoder 策略 → …
- SKILL.md covers 0. 本地日志入口快路径（先判类型，再分析）, 1. 数据源, 2. Clog decoder 策略 and 3. 生成时间线, plus 4 more sections
- Runs JavaScript scripts from its folder; calls node and npx
What it does
SDK Log Analysis is an agent skill from infometa/workbuddyskills. SDK 客户端日志分析 skill（带 Web 预览版）。用于本地 .clog/.xlog/文本日志的类型识别、二进制解码、TRTC/IM/TUI 客户端日志时间线解析，并提供本地日志 Web 预览服务。
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 73 other files, including scripts and reference files (for example `data/api/error-code.json`, `data/api/log-rule.json` and `data/api/timeline.json`).
The repository describes itself as: WorkBuddy skills / connectors / experts archive for offline study.
Example prompts
- “/sdk-log-analysis”
Requirements
- Node.js
Workflow steps
8 steps, taken from the step headings in SKILL.md.
- 本地日志入口快路径（先判类型，再分析）
- 数据源
- Clog decoder 策略
- 生成时间线
- 接口数据与参考文档
- 结论格式与安全输出
- Web 预览界面
- 禁止事项
What it can do on your machine
Read from SKILL.md and the folder at commit 75a5ad9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 5 files in scripts/ (JavaScript, from the files we listed), which the agent can run.
Shell commands in SKILL.md call:
nodenpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
SDK Log Analysis loads about 1.4k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 30 tokens; SKILL.md has 303 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 303 words (~1,428 tokens).
“本 skill 专注客户端日志：本地 .clog/.xlog 二进制解码、本地 TRTC / IM / TUI 日志文件时间线解析。TUI 指 TUICallKit、TUIRoomKit、TUILiveKit、TUIRoomEngine 等上层 SDK。timeline.js 支持 TRTC / IM / TUI 自动识别。服务端事件回调、云端录制/混流/转推链路不在本 skill 范围内。”
- name
- sdk-log-analysis
- version
- 0.1.0
- tags
- trtc, log-analysis, clog, timeline
- references
- references/web-log-patterns.md, references/native-log-patterns.md, references/miniprogram-log-patterns.md, references/audio-troubleshooting.md
Files
SKILL.md and 68 other files (scripts, references) in experts/sdk-log-expert/skills/sdk-log-analysis of infometa/workbuddyskills.
- SKILL.md
- .gitignore
- data/api/error-code.json
- data/api/log-rule.json
- data/api/timeline.json
- package.json
- references/README.md
- references/audio-troubleshooting.md
- references/miniprogram-log-patterns.md
- references/native-log-patterns.md
- references/web-log-patterns.md
- scripts/analyze-local.js
- scripts/evidence.js
- scripts/lib/aho-corasick.js
- scripts/lib/args.js
- scripts/lib/decoder.js
- … and 53 more
Open the folder on GitHubat commit 75a5ad9
Compare with similar skills
SDK Log Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| SDK Log Analysis this skillinfometa/workbuddyskills | 344 | — | ~1.4k | Automated safety check: Pass | None | |
| Growth Logaffaan-m/ECC | 275k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Clickhouse Logs Queriessupabase/supabase | 111k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Investigating LogsPostHog/posthog | 40k | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Logging and Error Reporting for Warpwarpdotdev/warp | 65k | 1 repos | ~5.6k | Automated safety check: Pass | AGPL-3.0 | |
| Analyze Logsactivepieces/activepieces | 25k | 1 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
- Official
Investigating Logs
PostHog/posthog
Investigate logs in a PostHog project: verify a service or deployment is healthy, explain an error spike, triage an incident, or understand what a log stream is saying.
Logging and Error Reporting for Warp
warpdotdev/warp
Guides log level choices and when to raise a structured Sentry event instead of a plain log line in the Warp Rust codebase, keeping secrets out of logs.
Analyze Logs
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
KubeSphere WizTelemetry Logging
kubesphere/kubesphere
Installs and configures WizTelemetry Logging for KubeSphere, with container log and optional disk log collection, dependency checks and the log query API.
More from infometa/workbuddyskills
All 212 skills in this repoCampus Event Playbook
infometa/workbuddyskills
This skill should be used when planning, coordinating, running, or reviewing student-led campus events, including club recruitment, freshman mixers, welcome activities, small talks, competitions…
Teachany
infometa/workbuddyskills
K-12 interactive courseware creation. An agent skill from infometa/workbuddyskills.
Weight Management HTML
infometa/workbuddyskills
A skill your agent uses when the adult weight-management MCP needs to be installed/set up in WorkBuddy (connector) or its result must be rendered as a standalone Chinese HTML plan.
Agent Browser
infometa/workbuddyskills
A skill your agent uses when the user needs browser automation, including opening web pages, taking screenshots, extracting page content, clicking elements, filling forms, or testing web flows.
AI Research Radar
infometa/workbuddyskills
定时任务：每日研究简报。漏掉重要论文和行业报告？每天帮你盯着，关键信息一条不漏 This skill should be used when the user asks about 定时任务：每日研究简报.
Check Deck
infometa/workbuddyskills
Investment banking presentation quality checker. An agent skill from infometa/workbuddyskills.
Questions about SDK Log Analysis
What does SDK Log Analysis do?
SDK 客户端日志分析 skill（带 Web 预览版）。用于本地 .clog/.xlog/文本日志的类型识别、二进制解码、TRTC/IM/TUI 客户端日志时间线解析，并提供本地日志 Web 预览服务。. SDK Log Analysis is an agent skill from infometa/workbuddyskills.
How do I install SDK Log Analysis in Claude Code?
Run `npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a claude-code`. Or copy the skill folder (experts/sdk-log-expert/skills/sdk-log-analysis in infometa/workbuddyskills) into .claude/skills/sdk-log-analysis in your project. Claude Code loads it when a task matches its description.
How do I install SDK Log Analysis in Codex?
Run `npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a codex`. Or copy the skill folder (experts/sdk-log-expert/skills/sdk-log-analysis in infometa/workbuddyskills) into .agents/skills/sdk-log-analysis in your project. Codex loads it when a task matches its description.
Can I use SDK Log Analysis in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add infometa/workbuddyskills --skill sdk-log-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sdk-log-analysis, .gemini/skills/sdk-log-analysis, .github/skills/sdk-log-analysis and .opencode/skills/sdk-log-analysis in your project.
What does SDK Log Analysis need to run?
Going by SKILL.md and its folder, SDK Log Analysis needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and npx). Our summary lists: Node.js.
Does SDK Log Analysis access the network?
SKILL.md contains no URLs. Its commands use npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is SDK Log Analysis safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does SDK Log Analysis use?
No licence was found for SDK Log Analysis or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does SDK Log Analysis use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 18k tokens, read only when the agent opens those files.
What are the alternatives to SDK Log Analysis?
Skills that share tags, products or a category with SDK Log Analysis: Growth Log (affaan-m/ECC, 275k stars), Clickhouse Logs Queries (supabase/supabase, 111k stars), Investigating Logs (PostHog/posthog, 40k stars) and Logging and Error Reporting for Warp (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains SDK Log Analysis?
infometa (a GitHub user) maintains it in infometa/workbuddyskills, which has 344 GitHub stars. The repository holds 212 skills in this directory. The repository was last updated on October 7, 2026.
Source: infometa/workbuddyskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.