Social Battery Monitor

Helps assess social energy, evaluate upcoming events' impact, and create realistic plans with boundaries and recovery to manage social overload.

Security Scan

The skill's code and runtime instructions align with its stated purpose (generating a social-energy plan), it requests no credentials or external installs, and it contains no network access or file writes — behavior appears coherent and proportional.

Purpose & Capability

Name/description match what the code and SKILL.md do: analyze user text or a small events dict and produce a Social Battery Plan. No unrelated credentials, binaries, or external services are requested.

Instruction Scope

SKILL.md instructs purely descriptive operations (assessment, planning, boundary phrases) and explicitly forbids calendar or message actions. The handler implements only local parsing and plan generation and does not access unrelated system files or network endpoints.

Install Mechanism

No install spec; this is instruction-only with bundled Python handler and tests. No downloads, package installs, or archive extraction are present.

Credentials

The skill requires no environment variables, credentials, or config paths. The code only reads its local SKILL.md file for metadata (benign), and otherwise uses inputs supplied at runtime.

Persistence & Privilege

always is false and the skill does not attempt to modify other skills or global agent configuration. It can be invoked autonomously (platform default) but has no broad privileges or credential access that would increase risk.

Assessment

This skill is internally consistent and implements only local input parsing and text generation — it doesn't send data externally or request secrets. You can install it with low risk from the perspective of credential or network exfiltration. As with any mental-health–adjacent tool, it should be used for descriptive planning only and not as a substitute for professional care; review outputs before acting on them. If you want extra assurance, inspect or run the included tests locally (tests/test_handler.py) to see sample behavior.

Social Battery Monitor / 社交电量监控师

Use this skill when a user is trying to balance connection, obligations, and recovery without crashing socially.

What it helps with

• Naming what social energy feels like when full, low, or depleted
• Spotting personal drain signals instead of using generic labels
• Reviewing upcoming events as nourishing, neutral, or draining
• Estimating energy cost by intensity, duration, closeness, and performance demand
• Adding pre-event buffers, exit strategies, and post-event recharge blocks
• Offering boundary phrases the user can actually say

Workflow

1. Ask how social energy usually feels when full, low, and depleted.
2. Identify early signs of drain, such as irritability, numbness, brain fog, or shutdown.
3. Review upcoming social events and label them by likely cost and value.
4. Estimate energy cost by intensity, duration, closeness, and required performance.
5. Add buffers, exit strategies, and recharge blocks.
6. End with a simple protection plan and a recharge menu.

Output format

# Social Battery Plan
## Current Battery
- Current level:
- Signs I am already low:

## Upcoming Social Load
- Event:
- Expected cost:
- Expected value:
- Recovery needed:

## Protection Plan
- Before the event:
- During the event:
- Exit line:
- After the event:

## Recharge Menu
- Quick recharge:
- Deep recharge:

Quality bar

• Use the user's own depletion cues, not generic personality labels.
• Include both recovery planning and boundary planning.
• Recognize that some social time gives energy rather than only draining it.
• Produce a workable plan for the next few days, not just abstract insight.

Limits

• Unavoidable work or family obligations may limit ideal choices.
• Users may feel guilt when protecting energy, so boundaries should be normalized.
• The goal is pacing, not total avoidance.
• Descriptive support only, with no calendar sync or message sending.