agentleFS
Sign inStart free
Runtime-3rr0rRuntime-3rr0r/canvas-scanner/skills/school-advisor/SKILL.md

school-advisor

Skill2 starsChanged 57 days agoMITView on GitHub

Use when asked anything about classes or the school week.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If asked something the brain can't answer from its index, refresh from sources once, answer, then note the gap to refresh in COURSE-BRAIN …

    line 27

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

Config: resolve <PLACEHOLDER> tokens from ~/.hermes/school-config.md (see canvas-course-sync → School config). Never edit SKILL.md with real values.

School Advisor (front door)

Front-door router for the school suite. When the user asks anything class-related ("what's next", "catch me up", course questions, "remind me about..."), route instead of guessing:

  1. Course question → read that course's COURSE-BRAIN.md first (see course-knowledge-base). Only open source files (README/Notes/Materials/Announcements) if the brain doesn't answer. Never re-scan folders by default.
  2. "What's my week / today / next" → answer from Roadmap.md (load-tags 🟢/🟠/🔴, balanced by day, pre-shifts). Roadmap IS the calendar — assignments and study blocks live there, no .ics/Outlook (lateralized 9/14).
  3. Stale or unknown data → trigger canvas-course-sync sweep first, refresh COURSE-BRAINs, then answer.
  4. Notes / studying → study-notes-workflow (pipeline incl. Gemini comparison + mastery log) or course-study-session for a session.
  5. Homework photos → photos-to-pdf → stage submission PDF in Downloads.
  6. Canvas-only platforms (Achieve/Pearson) → remind the user to self-check (they can't hold a pane login); log what they report.
  7. Dropped files / lost pile → the categorizer skill (school-inbox mode): file the drop, or report the Lost pile waiting for descriptions.

Always

  • Auto-log changes to Roadmap.md as they happen, no matter how small.
  • Weekly digest (Sunday anchor): render the digest from docs/weekly-digest-template.md — what changed, next-7-days from the Roadmap, weak spots from Mastery-Log, pending decisions (incl. Achieve/Pearson self-checks). It becomes the Sunday-review agenda; keep it conversational on top of the one file.

Pitfall

  • If asked something the brain can't answer from its index, refresh from sources once, answer, then note the gap to refresh in COURSE-BRAIN refresh rules — never answer from stale memory.

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