agentleFS
ankul5ankul5/internship-hunt-skill/skills/check-updates/SKILL.md

check-updates

Skill2 starsChanged 13 days agoLicence not identifiedView on GitHub

Everything about replies and follow-ups, in one place. Part A checks the user's authorized mail (Gmail API client, a Gmail connector, or pasted emails) since the last sync, a date, yesterday, today or the last seven days; skips messages already recorded; matches each to a tracked application with confidence scores; classifies interviews, assessments, rejections, offers, requests for information and recruiter replies; records them; updates status only on clear evidence; asks about anything ambiguous; and moves the checkpoint only after everything is saved. Part B finds sent messages with no reply, decides from recorded times and the user's approved timing whether one follow-up is appropriate, drafts it, and sends it only after the user approves that exact text. Use only when the user asks to check for updates or replies, or about follow-ups.

4 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.