Dfx Analyze

Analyze an onboard run's performance/scheduling/dependency/dump data using simpler's BUILT-IN DFX tools (simpler_setup.tools.*) instead of hand-rolling instrumentation. Use AFTER an onboard run when you need per-run device timing (Total/Orch/Sched), AICPU scheduler-overhead / Tail-OH breakdown, the task dependency graph, scope ring-fill peaks, or to inspect args dumps. These are simpler's own tools (shipped in the wheel), distinct from any cross-repo workload. Reach for this before writing custom timing/logging into the runtime.

49 stars 102 forksWriting & Content

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add hw-native-sys/simpler --skill dfx-analyze
Manual install
git clone --depth 1 https://github.com/hw-native-sys/simpler.git /tmp/simpler
mkdir -p ~/.claude/skills
cp -r /tmp/simpler/.claude/skills/dfx-analyze ~/.claude/skills/dfx-analyze

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Analyze DFX data (simpler's own tools)

simpler already ships end-user analysis CLIs under `simpler_setup.tools` —
**use them; do not re-invent timing/instrumentation in the runtime.** Canonical
reference (tool flags, examples, output paths): `simpler_setup/tools/README.md`.
Per-DFX docs: `docs/dfx/` (`l2-timing.md`, `sched-overhead-model.md`,
`chip-swimlane-profiling.md`, `scope-stats.md`, `dep-gen.md`, `args-dump.md`).

## Pick the tool by question

| You want… | Tool | Needs |
| --------- | ---- | ----- |
| Per-run **Host / Device / Effective / Orch / Sched** timing | `strace_timing --rounds-table` | nothing extra — `[STRACE]` markers are on stderr (`SIMPLER_HOST_STRACE`, compile-time default on, **NOT** gated by swimlane) |
| AICPU **scheduler overhead / Tail-OH / critical-path** breakdown | `sched_overhead_analysis` | a `--enable-chip-swimlane` (level≥3) run + `--enable-dep-gen` run |
| Swimlane → **Perfetto** Chrome trace | `swimlane_converter` | `--enable-chip-swimlane` run (`--overhead` track needs deps.json too) |
| Task **dependency graph** (text / HTML) | `deps_viewer` | `--enable-dep-gen` run → `deps.json` |
| **Per-scope ring-fill peaks** (task_window / heap / tensormap) | `scope_stats_plot` | `--enable-scope-stats` run → `scope_stats.jsonl` |
| Inspect / export **args dumps** | `dump_viewer` | `--dump-args` run → `args_dump/` |

## First reflex: Host/Device/Orch/Sched needs nothing extra
Read the full skill on GitHub

Details

Skill name
dfx-analyze
Path
.claude/skills/dfx-analyze/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Dfx Analyze skill do?

Analyze an onboard run's performance/scheduling/dependency/dump data using simpler's BUILT-IN DFX tools (simpler_setup.tools.*) instead of hand-rolling instrumentation. Use AFTER an onboard run when you need per-run device timing (Total/Orch/Sched), AICPU scheduler-overhead / Tail-OH breakdown, the task dependency graph, scope ring-fill peaks, or to inspect args dumps. These are simpler's own tools (shipped in the wheel), distinct from any cross-repo workload. Reach for this before writing custom timing/logging into the runtime.

How do I install the Dfx Analyze skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add hw-native-sys/simpler --skill dfx-analyze. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dfx Analyze popular?

It lives in hw-native-sys/simpler, which has 49 GitHub stars and 102 forks.

Related skills

Benchmark

49

hw-native-sys/simpler

Benchmark runtime performance on hardware. If the current branch has commits ahead of upstream/main or uncommitted changes, compares against the fork point (merge-base). Otherwise benchmarks current state only. Use when the user asks to benchmark, measure performance, or compare latency.

Git & Code Review102

Checkout PR

49

hw-native-sys/simpler

Add a remote for a given PR's head repository and checkout a local pr-xxx-work branch. Use when the user wants to work on someone else's PR locally.

Git & Code Review102

Clean Branches

49

hw-native-sys/simpler

Remove stale local and remote git branches that have been merged into main. Detects regular merges and squash merges. Cleans up fork remote branches and prunes tracking refs. Use when the user asks to clean up branches, remove merged branches, or tidy up git.

Git & Code Review102

File Bug

49

lllyys/vreader

Create a GitHub issue for a bug row in docs/bugs.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing bug row, or asks 'create issue for bug #N', 'file bug 115', 'mirror bug 42 to GH', 'this bug needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/bugs.md` row because it lacks `GH: #N`. Stays strictly in the mirror-an-existing-row scope — do not use for triaging new bugs (that's the triage skill) or fixing bugs (that's fix-issue).

Writing & Content21

Website Visitor Identification

79

LeadMagic/gtm-skills

Design website visitor identification and deanonymization programs — company vs person-level ID, vendor selection (Clearbit/Breeze, RB2B, 6sense, etc.), privacy guardrails (GDPR/CCPA operational), Slack alert triage, and ICP routing to MQL or outbound triggers. Use when implementing visitor ID, reverse-IP reveal, intent data, or person-level LinkedIn visitor tracking. Triggers on: "visitor identification", "deanonymization", "website intent", "Clearbit Reveal", "RB2B", "who visited our website", "reverse IP", "WebSights", "Leadfeeder", "visitor ID privacy".

Writing & ContentIn 1 list18

Offer Guarantee

49

Liamrjohnston/offer-master-skill

Designs one fair, capped guarantee aimed at the buyer's main fear. Picks the type, sets the measure, conditions and cap, writes the exact words and claim steps, and costs it if 1 in 10 claim.

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.