agentleFS
askoulwassimaskoulwassim/perfect-placement/skills/score/SKILL.md

score

Skill3 starsChanged 33 days agoMITView on GitHub

Score inbox roles. Call roles.score without criteria so Kev judges C1..C9 (blind for C1, C2, C3, C4, C9); judge them yourself only when Kev is unavailable. The engine does totals, bands, dealbreakers, affinity, the per-company cap and status moves.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use audit.

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.
  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 1

    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:

    Kev unavailable: If the call answers backend_unavailable ("Kev did not answer"), judge C1..C9 yourself:

    line 20
  2. Very specific:

    Call roles.score { role_id, criteria: { c1..c9 }, criteria_p?: { c1: 0.8, ...

    line 23
  3. Very specific:

    After a Work mode change, roles.reevaluate_filters { dry_run: true } lists work-mode archives that now pass.

    line 46
  4. Distinctive:

    Never moves on-deck or later backwards.

    line 48

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

score

You supply judgment. roles.score supplies mechanics. Never compute a total, band, affinity, cap or status yourself.

Inputs

  • Roles in inbox (roles.list { status: 'inbox' }) or roles a profile change asks to rescore. A run started for one role (role_id given) scores that role only; a run without one scores every inbox role.
  • The JD for each role (roles/<role_id>.md in the vault; capture the full JD first if only a title is on file).
  • The current profile (profile.get): Craft, Domain, Team, Growth, Terms, Work mode, Dealbreakers.

Steps per role

  1. Facts. Extract, never guess: workplace (remote | hybrid | onsite | flexible | unspecified), remote_ok (true | false | null), location (where the role sits, as the JD says it, e.g. "New York, NY"), comp_min, comp_max, and dealbreaker_hits (hard nos from the Dealbreakers component the JD clearly hits; empty if none). Do not put work mode in dealbreaker_hits: the engine applies Work mode itself (accepted places, mode hard nos, remote only only when the profile sets remote_only). Unknown stays null; the engine flags it to verify.
  2. Let Kev judge (preferred). Call roles.score { role_id, facts, brand_terms?, notes? } without criteria. The engine asks the decision layer: one Kev call with the masked JD for C1, C2, C3, C4, C9 (company, products, domain and URLs replaced by [company]; add product names or founders in brand_terms) and one with the full state for C5..C8. Every criterion becomes a decision row (backend, p, latency) linked from the score.
  3. Kev unavailable. If the call answers backend_unavailable ("Kev did not answer"), judge C1..C9 yourself:
    • Blind pass (C1, C2, C3, C4, C9): mask the company name, products, domain and URLs as [company] and score from the masked JD only.
    • Open pass (C5, C6, C7, C8): now use the company: domain fit, comp vs Terms, team and leaders, growth ceiling.
    • Call roles.score { role_id, criteria: { c1..c9 }, criteria_p?: { c1: 0.8, ... }, facts, notes }. Each criterion is recorded as an agent decision (p from criteria_p, else your call's confidence, else 0.75). When Kev answers it gives a second opinion; gaps over one point are flagged on the score (facts_json.disagreements) and the Role screen.
  4. No agent and no Kev (a human calling the op): the nine questions go to Needs you and the op answers requires_human. Once they are resolved, roles.score again uses the human answers.
  5. Notes hold one line per criterion and go to the role markdown.

Criteria (1 to 5)

IdLabelBlind15
c1Decisionsyesfar from strategyat the table
c20-to-1yesmaintenancegreenfield
c3Externalyesinternal onlycustomer or market facing
c4Datayesincidentaldata or AI is the product
c5Domainnopoor fitideal problem space
c6Compnowell below floorat or above target
c7Teamnoweakexceptional
c8Growthnocappedopen
c9Shapeyeswrong function or levelexact

What the engine does (do not repeat it)

  • Weights from the profile version; total, band (green 75, yellow 55).
  • Company affinity nudge, capped at config.scoring.affinity_cap. A company you love does not raise C1..C9.
  • Dealbreakers gate first. No company bypasses a dealbreaker, dream company or not. Work mode: hybrid in an accepted place passes; hybrid elsewhere is a verify flag unless the profile says fail; a mode hard no fails; unknown mode is a verify flag.
  • After a Work mode change, roles.reevaluate_filters { dry_run: true } lists work-mode archives that now pass; without dry_run it queues a Needs-you restore per role. Never restore a role yourself.
  • Per company, the top config.scoring.company_active_cap roles stay active; the rest go held and are promoted automatically when a slot frees.
  • Never moves on-deck or later backwards. Records profile version and rubric snapshot on every score.
  • Records who judged each criterion in facts_json.criteria_source (kev, agent or human, with p and the decision id) and, for agent criteria, second_opinion (kev or unavailable) and disagreements.

Tools

A headless run pre-approves exactly these (SKILL_GRANTS in packages/engine/runners/grants.ts; a test keeps this list and that one equal) and denies everything else. If one you need is denied or missing, do not work around it: runs.finish { run_id, status: "error", summary: { error: "tool denied: <tool>", denied_tools: [...] } }.

  • {{tool:pp}}: the pp MCP tools (every Perfect Placement read and write is an op).
  • {{tool:web.fetch}}: capture the full JD from the posting when only a title is on file.

Rules

Supply judgment only; every write is an op. Never submit an application or send an email.

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.