agentleFS
jhonatan-oliveiradevjhonatan-oliveiradev/agent-skills/skills/evaluating-developer-proficiency/SKILL.md

evaluating-developer-proficiency

Skill1 starsChanged 3 months agoMITView on GitHub

Use when a developer must demonstrate a target capability level against a versioned assessment blueprint, observable rubric criteria, and explicit evidence gates.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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 the criteria are missing or ambiguous, do not silently invent them.

    line 20
  2. Distinctive:

    Keep challenge scope proportional to the criterion being tested.

    line 25
  3. Distinctive:

    Use language such as Skill Assessment or Proficiency Report, not accredited certification.

    line 44

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

Evaluating Developer Proficiency

Evaluate demonstrated capability against a fixed blueprint. Observe evidence first, apply deterministic gates second, and report uncertainty instead of producing an unconstrained model score.

Require an evaluation contract

Before evaluating, identify:

  • capability and target level;
  • blueprint or explicit criterion version;
  • required evidence dimensions;
  • challenge types;
  • observable rubric criteria;
  • blocking gates and minimum evidence;
  • retest policy when applicable.

If the criteria are missing or ambiguous, do not silently invent them.

Assemble evidence-producing challenges

Choose challenges that can reveal the required dimensions: concept knowledge, code reading, debugging, implementation, or technical reasoning. Avoid multiple-choice-only evaluation when performance is required.

Keep challenge scope proportional to the criterion being tested. Do not add irrelevant difficulty to make an assessment feel rigorous.

Observe before judging

Record what the candidate actually demonstrated for each rubric criterion. Preserve failed gates, partial demonstrations, contradictions, and provenance. Separate evaluator interpretation from the raw response or artifact.

Apply gates and derive the result

Determine whether required criteria and evidence classes are satisfied. A strong average cannot compensate for a failed blocking dimension. Keep proficiency and confidence separate, and cap confidence when provenance is external or unverified.

Produce a structured report

Return:

  • blueprint/version;
  • target and demonstrated level;
  • confidence;
  • criterion observations;
  • evidence/provenance;
  • failed or uncertain gates;
  • actionable next gaps;
  • retest recommendation when useful.

Use language such as Skill Assessment or Proficiency Report, not accredited certification.

Ownership boundaries

This method owns assessment assembly, rubric-based observation, gate application, structured results, and feedback. It does not redefine level criteria ad hoc, sequence a career roadmap, or use free-form model scoring as the final authority.

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.