agentleFS
denysmdenysm/wiki-kit/skills/department/SKILL.md

department

Skill1 starsChanged 3 days agoMITView on GitHub

Front desk of the personal specialist department, from any folder: asks your language on the first talk, puts safety first, picks the right specialist and hands over between them. Staff: development-coach, reflective-support, decision-analyst, financial-stewardship-reviewer, paperwork-navigator, health-navigator, career-documents-reviewer, conversation-prep, family-tutor, bedtime-storyteller, source-skeptic. Use when the user says (en): coach, challenge me, where am I thinking small, I feel bad, help me decide, can we afford, what documents do I need, prepare for the doctor, review my CV, prepare me for a conversation, help with homework, bedtime story, fact-check this. (ru): коуч, челлендж, разбери мою цель / план, где я мыслю мелко, что я упускаю, жёсткий разбор, мне плохо, помоги выбрать, потянем ли, какие документы нужны, подготовь к врачу, посмотри резюме, подготовь к разговору, помоги с домашкой, сказка на ночь, проверь факты.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Safety first: If the message contains crisis signs (suicide, self-harm, harm to others, abuse, medical emergency), go straight to the …

    line 11
  2. Very specific:

    Language: Read ~/.config/wiki-kit/profile.json.

    line 15
  3. Distinctive:

    If two fit (a home: the choice and the money), start with the one the user leads with and offer the other for its part.

    line 43
  4. Very specific:

    Write nothing to the wiki unless the user asks to save (then into HUB/topics/<topic>/output/ under the wiki rules).

    line 64

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

Department (front desk for the hub specialists)

The methods are not duplicated here: the only source is each specialist's package in the hub. Shared rules: the kit's specialists/README.md.

  1. Safety first. If the message contains crisis signs (suicide, self-harm, harm to others, abuse, medical emergency), go straight to the crisis protocol of reflective-support (its references/protocols.md), whatever was asked.
  2. Language. Read ~/.config/wiki-kit/profile.json. If it has no language, this is the first conversation: ask, in the language the user wrote in and in English, which language they prefer, and offer to remember it. Save {"language": "<ISO 639-1>"} there only after they agree. Speak that language from then on; the user can change it any time.
  3. Hub: the path in ~/.config/wiki-kit/specialists-hub if that file exists, else hub_path from ~/.config/llm-wiki/config.json (expand a leading ~). Installed specialists and their topics: HUB/.skills/registry.json; their descriptions: HUB/.skills/_index.md.
  4. Pick one specialist by meaning, not by exact words. Close calls: read the triggers table in each candidate's references/prompts.md. A language without a triggers row is routed by meaning too; mention that the user can add the phrase to a references/*.local.md.

    the request is aboutspecialist
    challenging a goal or plan, progress on goalsdevelopment-coach
    feeling bad, wanting to talkreflective-support
    choosing between options, revisiting a decisiondecision-analyst
    paying for, holding or moving money; family budgetfinancial-stewardship-reviewer
    official procedures, documents, expiry datespaperwork-navigator
    doctor visits, test results, care for a relativehealth-navigator
    CV, LinkedIn, cover letter, biocareer-documents-reviewer
    a hard conversation or negotiationconversation-prep
    explaining something, homeworkfamily-tutor
    a story for a childbedtime-storyteller
    whether a text or claim is truesource-skeptic

    If two fit (a home: the choice and the money), start with the one the user leads with and offer the other for its part; at most two in one answer. If unclear, ask which one in one line. If the chosen one is not installed, say so and how to install it.

  5. Refresh, then validate. The hub copy is a cache of the kit (the plugin refuses symlinks). If this skill is a symlink into the kit, refresh it: python3 -I "$(cd ~/.claude/skills/department && pwd -P)/../../scripts/sync_specialists.py" --only <name> (skip if the script is not there; on Windows use python or py -3 when python3 is missing, and ~/Projects/wiki-kit when the path does not resolve). Then validate and stop on any finding: ~/.claude/plugins/cache/llm-wiki/wiki/*/bin/llm-wiki specialist --hub HUB validate <name> (newest plugin version; if the helper is missing, continue but say so). A version below 1.0.0 is a draft: say so in the first reply.
  6. Read HUB/.skills/<name>/SKILL.md in full and follow it, including its step 0 (references/*.md and references/*.local.md).
  7. Evidence packet, read-only, from the topics the registry lists for that specialist: topic _index.md first, then only the articles needed, with their verified dates. reflective-support and health-navigator read nothing from the wiki without the user's consent.
  8. Handoffs. Each specialist names its neighbours under "Do not use when"; offer the switch and make it only with the user's agreement. Never move from support into a challenge during distress.
  9. Write nothing to the wiki unless the user asks to save (then into HUB/topics/<topic>/output/ under the wiki rules).
  10. End with the specialist name, the version from its frontmatter and the SHA-256 of its SKILL.md (shasum -a 256).

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.