agentleFS
jurgendnjurgendn/agent-skills/skills/academic-career/apply-program-theme-extractor/SKILL.md

apply-program-theme-extractor

Skill10 starsChanged 57 days agoNo licenceView on GitHub

Determine what a programme, track, specialisation pathway, doctoral school, or funding call actually selects for — its declared theme, or, where none is published, its operative theme inferred from official evidence. Use whenever the user asks "what is this programme's theme", "what does this call actually want", "is this track themed or open", "the landing page doesn't say what they focus on", "what do these 12 programmes each specialise in", or wants a candidate list of targets characterised before any of them is compared against a profile. Works applicant-free and over many targets at once, producing a reusable theme dossier per target. Distinct from apply-program-fit-mapper, which needs the applicant's evidence and issues the four-way fit verdict — route there once a profile enters. Distinct from apply-research-direction-mapper, which maps one person's research direction rather than an institution's selection scope. Also builds, on request for shortlisted targets, a programme profile kept apart from the theme — the programme's verified selling points, the graduate it intends to produce, and its expected learning outcomes — for questions like "why should I choose this track", "what makes this programme different", "what kind of graduate does this scholarship want to produce", "what will I actually learn there", or material for a "why this programme" paragraph or interview answer.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.