Crypto & Web3  ·  Curated marketplace

cost-export

Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards)


Composite

3.1

C 4.0 · A 2.5

How we got there

Craft · D1–D5

D1 · Trigger clarity 4.0
D2 · Output specificity 4.5
D3 · Scope precision 4.5
D4 · Self-containment 3.5
D5 · Reusability 3.5

Adoption · A1–A5

A1 · Maintenance 2.5
A2 · Documentation 1.0
A3 · License 2.5
A4 · Adoption 4.7
A5 · Authorship 2.0

02 — Review

Our evaluation


Tier-2 Review: cost-export (crypto-web3 cluster)

What We Attempted

We evaluated the cost-export skill from the ruvnet-ruflo-plugins-ruflo-cost-tracker-skills-cost-export-skill-md repository, which aims to export cost-tracking telemetry in Prometheus textfile or webhook JSON formats for external observability tools like Grafana and Datadog. The skill received a composite score of 4.0/5.0 from automated dimension analysis, with strong marks in trigger clarity (4.0), output specificity (4.5), and scope precision (4.5), but slightly lower scores in self-containment (3.5) and reusability (3.5). The auto-summary described it as having good trigger clarity, specific output, focused scope, mostly self-contained, and moderately reusable.

What Failed

Our test harness ran two critical validation tests against the SKILL.md file, and both failed:

  1. install (fail): The SKILL.md contains no installation instructions. The skill is not published on PyPI, and no pip install, npm install, or other package manager commands are documented. Without installation guidance, users cannot acquire the skill's dependencies or runtime environment.

  2. smoke-invocation (fail): The SKILL.md provides no CLI entry point, invocation example, or usage demonstration. There is no --help flag, no cost-export command shown, and no minimal working example. This makes it impossible to determine even the most basic invocation pattern, such as what arguments or flags are required to produce the promised Prometheus textfile or webhook JSON output.

What We Observed

The SKILL.md content (truncated to 4000 characters) describes the skill's purpose clearly: "Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards)." The description is well-written and the intended functionality is plausible. However, the document reads like a concept note or a high-level specification rather than an executable skill definition. It lacks:

  • Concrete installation steps
  • Dependency declarations (none were observed, but no package.json, requirements.txt, or similar file was referenced)
  • Example invocations
  • Configuration parameters or environment variables
  • Error handling or edge case documentation

The skill appears to be designed as part of a larger "ruflo" plugin ecosystem, but the standalone SKILL.md does not provide enough information to use it independently.

Rating Assessment

Given that 0 of 2 tests passed, the composite score of 4.0/5.0 is theoretical until the installation and invocation failures are resolved. The dimension scores may be accurate in terms of the skill's conceptual design (clear trigger, specific output, focused scope), but they cannot be validated against real-world usability. The self-containment and reusability scores of 3.5 each are likely overestimates given the lack of installation and usage documentation, which are prerequisites for both.

Is the Skill Valuable in Principle?

Yes. The concept of exporting cost-tracking data to Prometheus or webhook JSON for integration with Grafana and Datadog is a common and valuable need in cloud cost management, particularly in blockchain and Web3 contexts where on-chain transaction costs can be significant. If the skill were properly documented with installation steps and invocation examples, it could serve a useful niche. The core functionality — transforming internal cost data into standard observability formats — is technically straightforward and would save users from building custom exporters.

However, in its current form, the skill is unusable. A physical re-run after the author provides installation instructions and at least one working invocation example would be required to confirm whether the implementation actually works as described. Until then, this review serves as an honest signal of incomplete documentation rather than a takedown of the underlying idea.

03 — Tests

What we tried


Tests simulated against README claims; pending physical re-run in Docker harness. Ran 2026-07-06.

Overall: broken. 0 tests passed, 0 partial, 2 failed; key blocker: SKILL.md lacks installation instructions and invocation examples.

Test Status Notes
install fail No install command documented in SKILL.md; package not on PyPI.
smoke-invocation fail No CLI entry point or invocation example provided in SKILL.md; cannot determine minimal invocation.
04 — Cross-validation

1 source verified

Install

Use this skill

/plugin install cost-export