agentleFS
Sign inStart free
lyh843lyh843/AgentSkills/skills/battery-status/SKILL.md

battery-status

Skill1 starsChanged 5 months agoMITView on GitHub

Check the current battery and charging information on this Linux machine, especially when the user asks for charging wattage, battery percentage, charging state, voltage, estimated time to full, or a compact power-status summary. Use when the user invokes $battery-status or asks to view laptop battery or charging power from the local system.

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to read the local machine's battery and AC adapter status and report it in a fixed compact format.

    line 9
  2. Very specific:

    Run scripts/check_battery.sh.

    line 12
  3. Distinctive:

    If the script returns battery information, present the output directly and add at most one brief note if needed.

    line 13
  4. Very specific:

    If the script reports that upower is missing or no battery is present, say that clearly instead of guessing.

    line 14
  5. Distinctive:

    Prefer the script output over hand-written parsing in the reply.

    line 30
  6. Very specific:

    Treat energy-rate as the battery-side charge or discharge power, not necessarily the charger's wall power.

    line 31
  7. Distinctive:

    If the battery is charging, label the power line as current charging power.

    line 32
  8. Distinctive:

    If the battery is discharging, label the power line as current discharge power.

    line 33
  9. Distinctive:

    Keep the answer concise.

    line 34

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

Battery Status

Overview

Use this skill to read the local machine's battery and AC adapter status and report it in a fixed compact format.

Workflow

  1. Run scripts/check_battery.sh.
  2. If the script returns battery information, present the output directly and add at most one brief note if needed.
  3. If the script reports that upower is missing or no battery is present, say that clearly instead of guessing.

Output Format

Return the result as a short block with these fields when available:

  • Timestamp
  • AC Online
  • Battery State
  • Battery Percentage
  • Charging Power
  • Voltage
  • Energy
  • Time To Full
  • Time To Empty
  • Cycle Count

Rules

  • Prefer the script output over hand-written parsing in the reply.
  • Treat energy-rate as the battery-side charge or discharge power, not necessarily the charger's wall power.
  • If the battery is charging, label the power line as current charging power.
  • If the battery is discharging, label the power line as current discharge power.
  • Keep the answer concise.

Fast Prompt Patterns

  • Use $battery-status to check my current charging power.
  • Use $battery-status to show my battery summary.
  • Use $battery-status to tell me whether I am charging and at what wattage.

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