doctor

Report latest package versions and release dates from doctor.json.

Updated Sep 12, 2021
One-click install
npx skills add https://github.com/cerico/macfair --skill doctor-cerico
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doctor
Source: https://github.com/cerico/macfair/tree/main/files/claude/skills/doctor
Command: npx skills add https://github.com/cerico/macfair --skill doctor-cerico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and operators avoid manual checks by reading a local memory state file and surfacing the latest package versions and their release dates from the daily doctor check.

Core Features & Use Cases

  • Read and parse the memory file at ~/.claude/MEMORY/State/doctor.json to extract current versions for tracked packages.
  • Report versions along with their release dates to support quick updates, inquiries, and release planning.
  • Include the timestamp of the last check to provide context and traceability.

Quick Start

Run the doctor skill to read ~/.claude/MEMORY/State/doctor.json and report the latest versions with their release dates, including when it was last checked.

Frequently Asked Questions about doctor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the latest package versions and release dates for my tracked dependencies?

This Skill reads the local file ~/.claude/MEMORY/State/doctor.json to report the latest package versions and their release dates, including the timestamp of the last daily check for development and operations workflows.

How do I view the last performed check timestamp for tracked package updates?

The Skill parses the doctor.json memory state file and reports the exact timestamp of when the daily version tracking check was last executed alongside the current versions and release dates.

Does this version tracking tool require any external dependencies to report package updates?

No external dependencies are required. The Skill relies entirely on reading the local memory state file doctor.json to surface version statuses and release dates for tracked packages without any additional installations.

What is the best way to automate surfacing release dates for npm packages in development workflows?

The best way is to use the daily doctor check file, which automatically extracts current versions and release dates for tracked packages to inform updates or release decisions without manual checks.

Why does the doctor check report stale package versions for my tracked dependencies?

The doctor check reports stale package versions if the daily check has not been updated recently. The Skill includes the last check timestamp from doctor.json to provide context and traceability for the current version data.