Agent skill

Development Task Telemetry

by Peiiii in Peiiii/nextclaw

A skill your agent uses when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard…

MITAuto-check passed

Install Development Task Telemetry

skills CLI
$ npx skills add Peiiii/nextclaw --skill development-task-telemetry -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Peiiii/nextclaw development-task-telemetry --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Peiiii/nextclaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/wiki/skills/process/development-task-telemetry .claude/skills/development-task-telemetry && rm -rf skills-src

Use ~/.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/

Facts

Skill name
development-task-telemetry
GitHub stars
260
Token cost
~802 tokens
SKILL.md length
181 words
Files
14 (incl. scripts)
Skills in repo
70
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard…

  • A development task needs visible phase tracing
  • SKILL.md covers 定位, 激活, 固定合同 and AI 查询与汇报, plus 1 more section
  • Runs JavaScript scripts from its folder; calls pnpm
  • Phase-level Token measurement

What it does

Development Task Telemetry is an agent skill from Peiiii/nextclaw. Use when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard from Codex rollout logs.

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including scripts (for example `agents/openai.yaml` and `dashboard/task-telemetry-dashboard.js`).

The repository describes itself as: A human-centered long-term AI partner—not a task-centered assistant. The licence is MIT.

When your agent uses it

  • A development task needs visible phase tracing
  • Phase-level Token measurement
  • Model/effort comparison
  • A deterministic usage report

Example prompts

  • “/development-task-telemetry”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit d130133. 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 9 files in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, 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

Development Task Telemetry loads about 802 tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 181 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~802

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

The full file from Peiiii/nextclaw at commit d130133, republished under its MIT licence (© Peiiii). 181 words, ~802 tokens.

Download SKILL.mdSave it as .claude/skills/development-task-telemetry/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.
name
development-task-telemetry
description
Use when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard from Codex rollout logs.

Development Task Telemetry

定位

作为开发生命周期的只读 observer,声明可移植的任务/阶段边界。NextClaw 完整开发和授权发布默认启用;限定单阶段任务按需启用。只观察 lifecycle 已决定的状态,不改变阶段、返工、完成门或模型路由,不自报 Token 数值。

激活

  • 根任务加载本 Skill 后,以 task=start 激活;子 Agent 只有拿到父任务传入的 task-id 和当前 phase 后才能用 task=join 激活。
  • marker 必须附着在原本就要发送的进度或最终消息第一物理行,位于 [我严格遵守规则]、[深思模式] 等前缀之后;禁止为 marker 新增消息、模型调用或工具调用。
  • 只在真实 task / phase 转换时输出;同一阶段的普通进度不重复输出。
  • 加载失败时说明 telemetry unavailable 并继续开发,不得阻塞任务。
  • 触达 marker、解析或默认收尾汇报时,必须运行定向测试,并以真实 rollout 和同一 task-id 复验报告;静态规则检查不能替代。

固定合同

根任务开始:

text
[flow:<flow>][step:<phase>][nextclaw.dev/v1 task=start id=<task-id> name="<task-name>" type=<task-type> phase=<phase>]

子 Agent 加入:

text
[nextclaw.dev/v1 task=join id=<task-id> phase=<phase>]

当前线程切换阶段:

text
[step:<phase>]

子 Agent 离开:

text
[nextclaw.dev/v1 task=leave id=<task-id> status=<status>]

根任务结束:

text
[nextclaw.dev/v1 task=end id=<task-id> status=<status>]

字段顺序和拼写固定。flow 为 Lifecycle 已定的 standard、trivial、bugfix;task-type 只允许 feature、bugfix、small-change,不混用;phase 只允许 task-understanding、design、implementation、validation、review、delivery、retrospective;status 只允许 completed、blocked、cancelled、failed。进入新阶段时用原有进度回复首行的 [step:<phase>],正常进度不重复;返回旧阶段再次标记。若任务启动时 flow 尚未冻结,先省略 [flow:<flow>],在冻结后首次阶段切换时输出 [flow:<flow>][step:<phase>]。设计审查和实现审查都标 review,具体 mode 在正文说明。

根任务生成一次 dt- 加 8 位小写十六进制 task-id,并在 reopen 时复用。task-name 使用能让人直接识别目标的简短名称,建议 8–30 个字符,最多 64 个字符,不含 "、] 或换行;reopen 时保持原名称和类型。子 Agent 原样复用父任务 ID,禁止自行生成或重新分类。解析器继续兼容缺少 name 或 type 的历史 task=start marker,但新 marker 必须同时提供名称和类型;历史缺失值保持未知,不从自然语言猜测。

每条 assistant 消息首行最多一个机器 marker 和一组匹配的人类可读 flow/step 标记。新任务的 step 必须与机器 marker 阶段一致;后续阶段只需短 step,解析器仍兼容历史机器 phase marker。不要在首行示例、引用、用户内容、工具输出或总结中伪造 marker。

报告中的 current_phase 是根线程最后一次声明的阶段;retrospective_observation=entered 只证明消息宣告进入复盘,不能证明复盘质量或最终判断。已完成任务没有复盘阶段标记时显示 missing;旧任务缺 flow 时为 unknown,不追认其合规。Lifecycle 的完成门仍须核查显式复盘决定与证据。

AI 查询与汇报

用户说“查看统计”“这个任务用了多少 Token”或给出 task/thread/session ID 时,AI 是查询入口:自己定位并运行脚本,禁止把命令交给用户执行。定位顺序是显式 task-id、当前上下文最近的 marker、用户给出的 thread/session ID;仍有多个候选时先列出简短候选,不猜测归属。

text
node .agents/wiki/skills/process/development-task-telemetry/scripts/report-task-phase-usage.mjs --sessions-root ~/.codex/sessions [--thread <thread-id>] [--task <task-id>] [--format json]

AI 默认文本回答,需要比较或计算时用 JSON。按需报告给任务类型、总 Token、阶段占比、模型/effort、调用与工具轮次、耗时、覆盖率和警告;无 marker 时只报告可观察总量并说明不能可靠分阶段。

启用 observer 的根开发任务默认收尾汇报:把 task=end 附在完成进度首行,待该 frame 落盘后按 task-id 运行脚本,最终答复末尾附 Token:约 <total>(输入 <input> / 输出 <output>,覆盖率 <coverage>);只追加最关键警告。统计截止 task=end,后续 observer 开销不递归计入任务。

用户可关闭本任务汇报。数据不可用时说明原因,不重试或阻塞交付;跨线程只由根 AI 汇总一次。

本地大盘

用户说“打开开发任务统计大盘”时,AI 自己运行 pnpm development-task-telemetry:dashboard 并返回本地地址,禁止只把命令交给用户。服务只绑定 127.0.0.1,默认打开浏览器、按当前 Git workspace 与其 worktree 过滤 rollout,并每 15 秒自动刷新;重复启动复用同一 workspace 已运行的大盘。无浏览器环境才使用 --no-open。

© Peiiii, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 13 other files (scripts) in .agents/wiki/skills/process/development-task-telemetry of Peiiii/nextclaw.

  • SKILL.md
  • agents/openai.yaml
  • dashboard/index.html
  • dashboard/task-telemetry-dashboard.css
  • dashboard/task-telemetry-dashboard.js
  • scripts/lib/codex-rollout-adapter.mjs
  • scripts/lib/task-phase-analyzer.mjs
  • scripts/lib/task-phase-protocol.mjs
  • scripts/lib/task-phase-report.mjs
  • scripts/lib/task-telemetry-dashboard-server.mjs
  • scripts/report-task-phase-usage.mjs
  • scripts/report-task-phase-usage.test.mjs
  • scripts/serve-task-telemetry-dashboard.mjs
  • scripts/serve-task-telemetry-dashboard.test.mjs

Open the folder on GitHubat commit d130133

Compare with similar skills

Development Task Telemetry 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.

Development Task Telemetry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Development Task Telemetry this skillPeiiii/nextclaw260—~802Automated safety check: PassMIT
Observe Traceruvnet/ruflo74k—~522Automated safety check: NotesMIT
Telemetry AnalyticsOpenHands/OpenHands90k—~305Automated safety check: PassMIT
Telemetryrobinebers/openusage4.3k—~977Automated safety check: PassMIT
Tracezereight/gitlab-mcp2k1 repos~412Automated safety check: PassMIT
Distributed Tracingwshobson/agents40k11 repos~527Automated safety check: PassMIT

Similar skills

  • Observe Trace

    ruvnet/ruflo

    Trace agent execution by collecting spans and building a trace tree for a task

    74k GitHub stars~522 tokensUpdated today
    Auto-check: notes
  • Telemetry Analytics

    OpenHands/OpenHands

    This skill should be used when the user asks to "add tracking", "add a PostHog event", "change telemetry consent", "instrument onboarding", "debug analytics", or changes telemetry.ts…

    90k GitHub stars~305 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Telemetry

    robinebers/openusage

    Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running.

    4.3k GitHub stars~977 tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Trace

    zereight/gitlab-mcp

    Evidence-driven tracing with competing hypotheses in parallel.

    2k GitHub starsUsed in 1 repo~412 tokens
    DevelopmentAuto-check passed
  • Distributed Tracing

    wshobson/agents

    Implement distributed tracing with Jaeger and Tempo to track requests across microservices and identify performance bottlenecks.

    40k GitHub starsUsed in 11 repos~527 tokens
    DevOps & CloudAuto-check passed
  • Arize Trace

    github/awesome-copilot

    Official

    Downloads, exports, and inspects existing Arize traces and spans to understand what an LLM app is doing or debug runtime issues.

    40k GitHub starsUsed in 1 repo~5.9k tokens
    DevelopmentAuto-check: notes

More from Peiiii/nextclaw

All 70 skills in this repo
  • Nextclaw Skin Studio

    Peiiii/nextclaw

    A skill your agent uses when a user wants to browse, apply, inspect, create, refine, switch, or remove a NextClaw skin; wants a personal skin with arbitrary CSS, JavaScript, images, SVG, DOM…

    260 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • 当 NextClaw 产品更新后需要生成、替换、挑毛病或检查官网、GitHub README、用户文档或社交传播中的真实截图、AI 宣传视觉、整页 HTML 宣传预览、社区二维码等对外视觉资产时使用;也用于“更新截图”“重新截一批图”“做宣传页”“生成 campaign 页面”“视觉审稿”“五星挑刺法”或发布前检查视觉资产。普通站点布局开发或只写文章不触发。

    260 GitHub stars~801 tokensUpdated yesterday
    Auto-check passed
  • UI UX Pro Max

    Peiiii/nextclaw

    A skill your agent uses when the user wants professional UI/UX design guidance, design-system generation, UX review, or stack-specific frontend guidance through a bundled local UI/UX Pro Max dataset…

    260 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Impeccable

    Peiiii/nextclaw

    A skill your agent uses when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable…

    260 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Curate NextClaw skill resources, including OpenClaw and community sources.

    260 GitHub stars~479 tokensUpdated yesterday
    Auto-check passed
  • Mmx CLI

    Peiiii/nextclaw

    Use mmx to generate text, images, video, speech, and music via the MiniMax AI platform.

    260 GitHub starsUsed in 4 repos~2.7k tokens
    Auto-check passed

Questions about Development Task Telemetry

What does Development Task Telemetry do?

A skill your agent uses when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard…. Development Task Telemetry is an agent skill from Peiiii/nextclaw. Use when a development task needs visible phase tracing, task-level or phase-level Token measurement, model/effort comparison, or a deterministic usage report or local dashboard from Codex rollout logs.

When should I use Development Task Telemetry?

Development Task Telemetry fits situations like: A development task needs visible phase tracing; phase-level Token measurement; model/effort comparison; A deterministic usage report.

How do I install Development Task Telemetry in Claude Code?

Run `npx skills add Peiiii/nextclaw --skill development-task-telemetry -a claude-code`. Or copy the skill folder (.agents/wiki/skills/process/development-task-telemetry in Peiiii/nextclaw) into .claude/skills/development-task-telemetry in your project. Claude Code loads it when a task matches its description.

How do I install Development Task Telemetry in Codex?

Run `npx skills add Peiiii/nextclaw --skill development-task-telemetry -a codex`. Or copy the skill folder (.agents/wiki/skills/process/development-task-telemetry in Peiiii/nextclaw) into .agents/skills/development-task-telemetry in your project. Codex loads it when a task matches its description.

Can I use Development Task Telemetry 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 Peiiii/nextclaw --skill development-task-telemetry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/development-task-telemetry, .gemini/skills/development-task-telemetry, .github/skills/development-task-telemetry and .opencode/skills/development-task-telemetry in your project.

What does Development Task Telemetry need to run?

Going by SKILL.md and its folder, Development Task Telemetry needs JavaScript for the scripts in its folder and the command-line tools its instructions call (pnpm). Our summary lists: Node.js.

Does Development Task Telemetry access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Development Task Telemetry 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 Development Task Telemetry use?

Development Task Telemetry is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Development Task Telemetry use?

About 802 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Development Task Telemetry?

Skills that share tags, products or a category with Development Task Telemetry: Observe Trace (ruvnet/ruflo, 74k stars), Telemetry Analytics (OpenHands/OpenHands, 90k stars), Telemetry (robinebers/openusage, 4.3k stars) and Trace (zereight/gitlab-mcp, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Development Task Telemetry?

Peiiii (a GitHub user) maintains it in Peiiii/nextclaw, which has 260 GitHub stars. The repository holds 70 skills in this directory. The repository was last updated on October 6, 2026.

Source: Peiiii/nextclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.