RescueTime

Fetch productivity data from RescueTime. Use when the user asks about their screen time, productivity score, app usage, time tracking, how they spent their day/week, or wants reports on their computer activity. Requires API key in TOOLS.md or passed directly.

Security Scan

The skill appears to do what it claims (call RescueTime APIs) and is instruction-only, but it fails to declare or document the required credential in the registry and instructs storing the API key in a shared TOOLS.md, which is an important mismatch and privacy risk you should review before enabling.

Purpose & Capability

Name/description match the SKILL.md: all examples and endpoints target RescueTime and RescueTime data. However, the registry metadata lists no primary credential or required env vars while the SKILL.md explicitly requires an API key — this mismatch is unexpected and should be clarified.

Instruction Scope

Runtime instructions are narrowly scoped to calling RescueTime HTTP endpoints via curl and parsing responses. They do not instruct reading unrelated files, executing arbitrary binaries, or transmitting data to third-party endpoints other than rescuetime.com. Examples use shell date substitutions and place the API key in the query string.

Install Mechanism

There is no install spec and no code files — lowest-risk configuration: nothing is written to disk by the skill itself. This is coherent with an instruction-only integration.

Credentials

The skill requires a RescueTime API key according to SKILL.md but the registry lists no required env vars or primary credential. SKILL.md recommends storing the API key in TOOLS.md (a shared config), which could expose the secret to other components. The credential request is reasonable for the purpose, but the omission from metadata and the suggested storage location are problematic.

Persistence & Privilege

Skill is not always-enabled and is user-invocable; it does not request system-level persistence or modify other skills. One note: SKILL.md's guidance to place the API key in TOOLS.md implies persistent storage of the secret — verify how TOOLS.md is protected and whether other skills or processes can read it.

What to consider before installing

This skill is instruction-only and calls RescueTime APIs, which is coherent with its description — but it has two issues you should address before installing: (1) the package metadata does not declare the RescueTime API key even though the SKILL.md requires one, and (2) SKILL.md suggests storing the API key in TOOLS.md (a shared file), which could expose the key to other skills or logs. Ask the publisher where the key should be stored, prefer a scoped/secret storage mechanism (or an environment variable explicitly declared in the registry), and confirm the skill's source/homepage since none is provided. Also be aware the examples put the API key in the URL (query string), which can end up in logs; if possible use a header-based call or verify RescueTime's recommended secure usage. If you cannot verify origin or secret handling, restrict use to manual invocation only and avoid putting the API key in global/shared files.

Fetch productivity analytics from the RescueTime API.

Setup

Store API key in TOOLS.md:

### RescueTime
- API Key: YOUR_KEY_HERE

Get a key at: https://www.rescuetime.com/anapi/manage

API Endpoints

Analytic Data (main endpoint)

curl "https://www.rescuetime.com/anapi/data?key=API_KEY&format=json&perspective=rank&restrict_kind=activity"

Parameters:

• perspective: rank, interval, member
• restrict_kind: category, activity, productivity, efficiency, document
• interval: month, week, day, hour (only for interval perspective)
• restrict_begin / restrict_end: YYYY-MM-DD
• restrict_thing: filter to specific app/site/category

Daily Summary Feed

curl "https://www.rescuetime.com/anapi/daily_summary_feed?key=API_KEY"

Returns last 14 days with productivity_pulse (0-100), total_hours, categories.

Productivity Levels

• 2: Very Productive (coding, writing, Terminal, IDEs)
• 1: Productive (communication, reference, learning)
• 0: Neutral (uncategorized)
• -1: Distracting (news, shopping)
• -2: Very Distracting (social media, games)

Common Queries

Today's activity by app:

curl "https://www.rescuetime.com/anapi/data?key=API_KEY&format=json&perspective=rank&restrict_kind=activity&restrict_begin=$(date +%Y-%m-%d)&restrict_end=$(date +%Y-%m-%d)"

Productivity breakdown:

curl "https://www.rescuetime.com/anapi/data?key=API_KEY&format=json&perspective=rank&restrict_kind=productivity"

By category:

curl "https://www.rescuetime.com/anapi/data?key=API_KEY&format=json&perspective=rank&restrict_kind=category"

Hourly breakdown today:

curl "https://www.rescuetime.com/anapi/data?key=API_KEY&format=json&perspective=interval&restrict_kind=productivity&interval=hour&restrict_begin=$(date +%Y-%m-%d)&restrict_end=$(date +%Y-%m-%d)"

Response Format

{
  "row_headers": ["Rank", "Time Spent (seconds)", "Number of People", "Activity", "Category", "Productivity"],
  "rows": [[1, 3600, 1, "VS Code", "Editing & IDEs", 2], ...]
}

Convert seconds to hours: seconds / 3600

Tips

• Productivity pulse 75+ is good, 85+ is excellent
• Category view helps see broad patterns
• Use interval perspective with hour for time-of-day analysis
• Data syncs every 3 min (premium) or 30 min (free)