agentleFS
claude-office-skillsclaude-office-skills/skills/weather-automation/SKILL.md

Weather Automation

Skill433 starsChanged 10 months agoMITView on GitHub

Automate weather-based workflows, forecasts, alerts, and location-aware notifications

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Accuracy: Use reliable data sources

    line 149

≈ “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

Weather Automation

Automate weather-based workflows and notifications.

Core Capabilities

Current Weather

current_weather:
  location: "San Francisco, CA"
  # or coordinates
  lat: 37.7749
  lon: -122.4194
  
  response:
    temperature: 65°F
    feels_like: 63°F
    humidity: 72%
    wind_speed: 12 mph
    conditions: "Partly Cloudy"
    uv_index: 5

Forecast

forecast:
  location: "New York, NY"
  days: 7
  
  daily:
    - date: "2024-01-20"
      high: 45°F
      low: 32°F
      conditions: "Snow"
      precipitation_chance: 80%
      
  hourly:
    interval: 3  # hours
    periods: 24

Weather Alerts

alert_rules:
  - name: "Rain Alert"
    condition:
      precipitation_chance: "> 70%"
      within_hours: 6
    action:
      notify: slack
      message: "☔ Rain expected in next 6 hours"
      
  - name: "Freeze Warning"
    condition:
      temperature: "< 32°F"
    action:
      - notify: sms
      - trigger: home_assistant
        action: protect_pipes

Workflow Examples

Morning Briefing

morning_weather:
  trigger: daily at 6:30 AM
  actions:
    - get_forecast:
        location: home
        days: 1
    - send_notification:
        channel: slack_dm
        message: |
          🌤️ Good morning! Today's weather:
          High: {{high}}°F | Low: {{low}}°F
          {{conditions}}
          {{#if rain}}☔ Bring an umbrella!{{/if}}

Event Planning

event_weather:
  trigger: calendar_event_tomorrow
  condition:
    event_type: outdoor
  actions:
    - get_forecast:
        location: "{{event.location}}"
        date: "{{event.date}}"
    - if:
        precipitation_chance: "> 50%"
      then:
        - notify: organizer
          message: "Consider backup venue - rain likely"

Best Practices

  1. Caching: Cache frequent requests
  2. Units: Support both metric/imperial
  3. Accuracy: Use reliable data sources
  4. Alerts: Set sensible thresholds
  5. Location: Support multiple formats

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.