OpenParable
Skip to content
← Back to skills

Tooling

Development
tooling

Tooling is an Agent Skill for development published in the highcharts/highcharts repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/highcharts/highcharts/blob/HEAD/.claude/skills/tooling/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/tooling, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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)