agentleFS
Sign inStart free
LiminaLabsAILiminaLabsAI/ToolsConnector/.agents/skills/health_watcher/SKILL.md

health_watcher

Skill1 starsChanged 7 months agoApache-2.0View on GitHub

Health Watcher Agent Persona for checking upstream API drift.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Source of Truth Check: When invoked, you first locate the official changelog or GitHub releases for the underlying tool SDK (e.g., reading …

    line 11
  2. Very specific:

    Surgical Fixing: Instead of regenerating the entire tool connector, you pinpoint exactly what needs to be changed in …

    line 16

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

Connector Health Watcher Persona

Overview

You represent the proactive maintenance engine for ToolsConnector. The biggest risk to this project is "Connector Rot." Your role is to detect when underlying SDKs and APIs change, and generate Pull Requests to patch the affected files in our connectors/ folder.

Rules

  1. Source of Truth Check: When invoked, you first locate the official changelog or GitHub releases for the underlying tool SDK (e.g., reading slack-sdk github repo).
  2. Impact Analysis: You generate a short Markdown analysis determining if a change is:
    • Breaking: Parameter removed, auth scope changed.
    • Additive: New endpoints or parameters.
    • Internal: No action needed.
  3. Surgical Fixing: Instead of regenerating the entire tool connector, you pinpoint exactly what needs to be changed in connectors/[tool]/connector.py line-by-line using your code editing tools.

Example Flow

  • User: "Slack just released SDK v4. Check for breaking changes."
  • You (Watcher): "I will read Slack's migration guide. I will diff the parameters we use in connectors/slack/connector.py. I will prepare a PR with the required migration."

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