OpenParable
Skip to content
← Back to skills

Chart Visualization

Design

Chart Visualization is an Agent Skill for design published in the B-M-Capital-Research/honeclaw repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Render research-style PNG charts for trends, comparisons, distributions, and scatter relationships when a visual materially improves the answer

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/B-M-Capital-Research/honeclaw/blob/HEAD/skills/chart_visualization/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/chart-visualization-ddf43bbf, 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.

Chart Visualization

Use this skill when a chart will materially improve the answer. Do not render a chart just because it is possible.

Invocation

Call:

skill_tool(
  skill_name="chart_visualization",
  execute_script=true,
  script_arguments={"spec_json":"<JSON chart spec>"}
)

The script expects one JSON object string as spec_json.

Required Spec Fields

  • chart_type
  • title
  • series

Optional Spec Fields

  • subtitle
  • x_label
  • y_label
  • x_values
  • annotations
  • footnotes
  • palette
  • output_name

Supported Chart Types

  • line
  • area
  • bar
  • scatter
  • histogram
  • horizontal_bar

Series Shape

Each series item should usually be:

{
  "name": "Revenue",
  "values": [100, 120, 135]
}

You may optionally add a color.

Response Rules

  1. Only render a chart when the underlying numbers are concrete and the visual actually clarifies the answer.
  2. Keep v1 simple. Prefer one chart, at most two.
  3. After a successful render:
    • read artifacts
    • place the exact file:///abs/path/to/chart.png URI into the final answer where the chart should appear
    • do not wrap that URI in markdown link syntax, HTML <a> tags, or image syntax
    • add a short takeaway before and/or after the URI
    • do not expose raw debug output unless the user asked for it
  4. If rendering fails, artifacts are empty, or the chart would be misleading, answer in text only.
  5. Do not invent numbers just to make a chart.

Cross-Skill Usage

When another finance/research skill already has the needed numbers, that skill should hand off to this skill instead of describing the chart in prose only.