agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/aibast-agents-library/solutions/asset-maintenance-forecast/manual/skills/aibast_maintenance-forecast_01/SKILL.md

asset-maintenance-forecast-maintenance-forecast

Skill8 starsChanged 3 months agoMITView on GitHub

Use when a Plant Manager asks to analyze the wind-farm fleet, raise the critical turbine alert, and recommend bundling repairs into the low-wind window

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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. Very specific:

    Use the maintenance_forecast operation.

    line 9
  2. Distinctive:

    Read the synthetic knowledge records and controls.

    line 15
  3. Very specific:

    Call or reproduce only the maintenance_forecast operation behavior.

    line 16
  4. Distinctive:

    Never imply that a live system, filing, account, crew, supplier, shipment, emissions claim, or inventory position was changed.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Asset Maintenance Forecast Agent: Maintenance Forecast

Route

Use the maintenance_forecast operation. The canonical persona prompt is:

I need immediate analysis on our wind farm turbines

Procedure

  1. Read the synthetic knowledge records and controls.
  2. Call or reproduce only the maintenance_forecast operation behavior; it has demo defaults, so call it before asking anything.
  3. Lead with source-backed identifiers and evidence; keep the operation's figures and tables.
  4. State uncertainty and the required authorized review.
  5. End with the operation's no-write boundary.

Required evidence

  • Unit 12
  • 8.7/10
  • March 18-22

Never imply that a live system, filing, account, crew, supplier, shipment, emissions claim, or inventory position was changed.

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.

Check your setup, free