agentleFS
c-monganc-mongan/ireland-mcp/skills/cso-chart/SKILL.md

cso-chart

Skill2 starsChanged 19 days agoMITView on GitHub

Finds a Central Statistics Office (CSO) PxStat table through the Ireland MCP server, pulls a filtered slice of it and turns it into a chart-ready table plus a chart spec (Vega-Lite or a Markdown table) with full citation. Use when someone wants official Irish statistics (population, prices, CPI, employment, housing, migration, etc.) charted or tabulated over time or across areas.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If an argument shape is unclear, call ireland_describe with { "source", "operation" } first.

    line 22
  2. Very specific:

    Find the table: Call cso/cso_search_tables with { "query": "consumer price index", "limit": 10 }.

    line 30
  3. Very specific:

    Read the dimensions: Call cso/cso_get_table_metadata with { "table_code": "CPM01" }.

    line 32
  4. Very specific:

    Pull a small slice: Call cso/cso_get_data with table_code and filters mapping dimension codes to arrays of category codes, e.g.

    line 34
  5. Very specific:

    Always filter: requests over 10,000 cells are rejected.

    line 36
  6. Distinctive:

    Follow ../_shared/citations.md.

    line 54
  7. Distinctive:

    Never mix tables or units in one series.

    line 55
  8. Distinctive:

    If an index, state the base period (e.g.

    line 56
  9. Distinctive:

    If the right table is unclear, show the top 3 candidates and ask.

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CSO chart

Turn a question into a correctly filtered CSO table and a simple chart.

Related projects: None in the catalogue.

Calling the tools

Steps name each operation as source/operation (e.g. ppr/ppr_price_stats), using the typed tool name as the operation. On the default surface, run it with ireland_call, for example:

{ "source": "cso", "operation": "cso_search_tables", "args": { "query": "consumer price index", "limit": 10 } }

If an argument shape is unclear, call ireland_describe with { "source", "operation" } first; it returns the schema and an example. search, fetch and nearby are top-level tools. If the server was added with ?toolsets=<ids> or ?toolsets=all, the typed tool (e.g. cso_search_tables) can be called directly with the same args.

Steps

  1. Find the table. Call cso/cso_search_tables with { "query": "consumer price index", "limit": 10 }. Pick the table whose title, frequency and date range fit. Tell the user the code you chose.
  2. Read the dimensions. Call cso/cso_get_table_metadata with { "table_code": "CPM01" }. Note each dimension code (statistic, time, area, etc.) and the category codes you need.
  3. Pull a small slice. Call cso/cso_get_data with table_code and filters mapping dimension codes to arrays of category codes, e.g. { "table_code": "F1001", "filters": { "<dim code>": ["<cat code>"] } }. Always filter: requests over 10,000 cells are rejected. Keep limit modest (≤500).
  4. For census population by county, cso/cso_area_profile is a shortcut.
  5. Shape the data into rows of { period, series, value, unit }. Keep the unit from the table.
  6. Chart. Choose: line for time series, bar for areas/categories. Emit a Vega-Lite spec (see references/vega-lite.md) or, if the client cannot render charts, a Markdown table.

Output format

### <Table title> (<table code>), <series>, <first>–<last period>
<chart spec or table>
Notes: <unit>, <base period if an index>, <provisional flags>.
Sources
- CSO, table <code> "<title>" (CC BY 4.0), last updated <date from metadata>, retrieved <date>: <url>

Rules

  • Follow ../_shared/citations.md. Title the chart with the table code and period.
  • Never mix tables or units in one series. Never extrapolate or forecast.
  • If an index, state the base period (e.g. Dec 2023 = 100).
  • If the right table is unclear, show the top 3 candidates and ask.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.