Saucebox Registry
← Browse

@highcharts/tooling

B

Keep changes aligned with the existing Highcharts tooling stack and avoid introducing ad-hoc or inconsistent build/test infrastructure.

skillclaude

Install

agr install @highcharts/tooling --target claude

Writes 1 file into .claude/skills/, pinned to git-12f420c0.

  • .claude/skills/tooling/SKILL.md

Document

name: tooling description: Keep changes aligned with the existing Highcharts tooling stack and avoid introducing ad-hoc or inconsistent build/test infrastructure.

Highcharts Tooling Guardrails

Use this skill for changes in tools/, build scripts, test runners, or repository automation.

Rules

  1. Reuse existing tooling first:
  • Prefer npm scripts, gulp tasks, eslint/playwright setup, and existing helpers under tools/.
  • Do not add a new toolchain when equivalent behavior already exists.
  1. Keep stack consistency:
  • Prefer Node-based scripts for cross-platform support unless shell behavior is explicitly required.
  • Avoid adding repo-wide dependencies for one-off automation.
  1. Keep automation safe and predictable:
  • Default scripts to non-destructive behavior.
  • Require explicit confirmation flags for destructive replacements.
  • Support non-interactive CI mode.
  1. Verify tooling changes:
  • Add or update usage docs/help output (--help) for new scripts.
  • Include a minimal validation checklist in task/PR output with exact commands used.

Output format

For each tooling change:

  • Change
  • Why this stack choice
  • Validation command(s)

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-12f420c0ecf72026-07-31