agentleFS
shanraisshanshanraisshan/codex-cli-best-practice/.agents/skills/weather-svg-creator/SKILL.md

weather-svg-creator

Skill979 starsChanged 8 months agoMITView on GitHub

Creates an SVG weather card showing the current temperature and writes it to orchestration-workflow/weather.svg and orchestration-workflow/output.md

6 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 1 is common, 2 are distinctive, and 2 are very specific to this project.

  • 1

    Common

    Most of the 5 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create an SVG weather card displaying the temperature for a given city and write it to the output files.

    line 13
  2. Very specific:

    Write the SVG content to orchestration-workflow/weather.svg.

    line 37
  3. Very specific:

    Create the orchestration-workflow/ directory if it does not exist

    line 53
  4. Common:

    Use the exact temperature value and unit provided — do not re-fetch or modify the data

    line 73
  5. Distinctive:

    Keep the SVG design minimal and clean

    line 74

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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

Weather SVG Creator Skill

This skill creates an SVG weather card from provided temperature data.

Task

Create an SVG weather card displaying the temperature for a given city and write it to the output files.

Instructions

You will receive the temperature value, unit (Celsius or Fahrenheit), and city name from the calling context.

1. Create SVG Weather Card

Generate a clean SVG weather card with the following structure:

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 200" width="400" height="200">
  <rect width="400" height="200" rx="12" fill="#1a1a2e"/>
  <text x="200" y="50" text-anchor="middle" fill="#e0e0e0" font-family="system-ui" font-size="16">[City Name]</text>
  <text x="200" y="110" text-anchor="middle" fill="white" font-family="system-ui" font-size="48" font-weight="bold">[value]°[C/F]</text>
  <text x="200" y="150" text-anchor="middle" fill="#888" font-family="system-ui" font-size="12">[Current date and time]</text>
  <text x="200" y="185" text-anchor="middle" fill="#555" font-family="system-ui" font-size="10">Weather data from Open-Meteo API</text>
</svg>

Replace [value], [C/F], [City Name] with actual values from the input.

2. Write Output Files

Write the SVG content to orchestration-workflow/weather.svg.

Also write a markdown summary to orchestration-workflow/output.md:

# Weather Report

![Weather Card](weather.svg)

**Location**: [City Name]
**Temperature**: [value]°[C/F]
**Fetched At**: [Current date and time in ISO 8601 format]

> Weather data provided by [Open-Meteo API](https://open-meteo.com/)
  • Create the orchestration-workflow/ directory if it does not exist
  • Overwrite any existing content

Expected Input

Temperature value, unit, and city from the calling agent:

Temperature: [X]°[C/F]
City: [City Name]
Unit: [Celsius/Fahrenheit]

Expected Output

Two files written:

  • orchestration-workflow/weather.svg — SVG weather card
  • orchestration-workflow/output.md — Markdown report embedding the SVG

Notes

  • Use the exact temperature value and unit provided — do not re-fetch or modify the data
  • Keep the SVG design minimal and clean
  • Include a timestamp so the report is traceable
  • Output files go in the orchestration-workflow/ directory

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.