Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/doca-firefly
Use this skill when the user is operating the DOCA Firefly Service container on BlueField — picking the four PTP configuration axes (role / profile / domain / interface), wiring the BlueField PHC + host follower + consumer workload pairing, deciding whether PTP-grade time is even needed (vs. chrony / NTP), or debugging a Firefly deployment where PTP isn't syncing or the host clock isn't following. Trigger even when the user does not explicitly mention "DOCA Firefly" or "PTP" — typical implicit p
Passed 18 of 20 test cases with the skill, and 6 of 20 without it.
and 15 more in the full report
13 fixed7 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When configuring the PTP Monitor subsystem in DOCA Firefly, what internal monitor client type option is supported for MONITOR_CLIENT_TYPE?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies phc2sys as the internal monitor client type for the MONITOR_CLIENT_TYPE variable. | Missed | Passed |
The instructions your model reads when the skill loads.
Subsystem inventory (Run-12 correction, verified Run-13). DOCA Firefly is NOT just "a PTP daemon." The shipped
doca_firefly.yamlexposes six PTP-stack subsystems via environment variables, each with its own*_STATE,*_CONFIG_FILE, and (where relevant)*_INTERFACE/*_DEVICEknobs (the count is six because the PTP Monitor subsystem ships an internalphc2sysmonitor client that is distinct from the standalone PHC2SYS subsystem — both ship in the same container image):
- PTP (
PTP_STATE,PTP_INTERFACE,PTP_CONFIG_FILE) — theptp4ldaemon (or master, depending on profile) that drives the BlueField PHC.- PTP Monitor (
MONITOR_STATE,MONITOR_CONFIG_FILE,MONITOR_CLIENT_TYPE,MONITOR_CLIENT_PHC2SYS_INTERFACE,MONITOR_CLIENT_CONNECTION_TIMEOUT) — the monitor server + client surface; the internalphc2sysmonitor client (MONITOR_CLIENT_TYPE=phc2sys) is a real subsystem inside Firefly, not just a host-side concern.- PHC2SYS (
PHC2SYS_STATE,PHC2SYS_ARGS,PHC2SYS_CONFIG_FILE) — the container-internalphc2sysinstance; the bundle previously framedphc2sysas host-only, which is wrong.- PPS (
PPS_STATE,PPS_DEVICE) — the Pulse-Per-Second output (with the additionalenable_while_runninganddo_nothingstates beyond plain enable/disable).- SyncE (
SYNCE_STATE,SYNCE_INTERFACE,SYNCE_CONFIG_FILE) — Synchronous Ethernet frequency distribution; orthogonal to PTP.- Firefly Servo (
SERVO_STATE,SERVO_CONFIG_FILE) — the proprietary Firefly servo loop (alternative to the upstream linuxptp servo).The valid
PROFILEvalues are exactlydefault/media/telco-l2/custom(perdoca_firefly.yamlcomments) — the agent must not invent additional values. Subsystems configured asdefined_by_profileare controlled by the activePROFILE.
test cases passed, vs 6 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.