agentleFS
leoleolroleoleolro/career-os/.claude/skills/weekly/SKILL.md

weekly

Skill0 starsChanged 55 days agoMITView on GitHub

Weekly career review — hunt stats, pipeline movement, follow-ups due, learning progress, next week's 3 actions. Use when the candidate says "weekly", "review my week", "what's the plan", or on a Sunday/Monday check-in. "/weekly".

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, setup and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 4 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 6 projects that use this

  • SentrySkill

    onboard

    Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Run a fresh hunt if the last run is > 2 days old (zsh tools/daily.sh does hunt → details → rescore → insights → dashboard), then node …

    line 8
  2. Very specific:

    Read: this week's reports/hunt-*.md, data/pipeline.json (history entries this week), profile/achievements.md (new lines), …

    line 9
  3. Very specific:

    Write reports/weekly-<today>.md (one page):

    line 10

“Common” is measured: kept by at least 6 in 10 of the 17 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/weekly

  1. Run a fresh hunt if the last run is > 2 days old (zsh tools/daily.sh does hunt → details → rescore → insights → dashboard), then node tools/track.mjs due.
  2. Read: this week's reports/hunt-*.md, data/pipeline.json (history entries this week), profile/achievements.md (new lines), profile/certifications.md (exam dates), profile/career-context.md.
  3. Write reports/weekly-<today>.md (one page):
    • Pipeline movement — what changed, what's stuck > 14 days, follow-ups overdue.
    • Market this week — new Strong/Good jobs, sources that failed, anything closing soon.
    • Learning — cert progress (EDMCS → Claude Architect), achievements logged, what's missing from the resume.
    • Applications sent vs target (ask the candidate for their weekly target once; store it in preferences.json as weekly_application_target).
    • Next week: 3 actions — concrete, each with the slash command that does it.
  4. Summarise in chat in ≤ 12 lines. Ask nothing unless a decision is blocking.

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.