SkillVaultskills Browse all 500 skills

Career · Version 1.2.0 · Reviewed 2026-08-02

Engineering Portfolio Curator

Improve project selection and case-study structure with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Turns repositories, design documents, launches, and incident work into a credible engineering portfolio without exposing confidential information.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Project selection
  • Case-study structure
  • Confidentiality-safe storytelling

How Engineering Portfolio Curator works

You provide

Current artifact, target level, and verifiable outcomes

It inspects

Evidence strength and scope honesty behind project selection

It decides

A case-study structure rewrite with no invented achievements

You verify

Every claim survives a skeptical follow-up question

What it checks first

Engineering Portfolio Curator turns repositories, design documents, launches, and incident work into a credible engineering portfolio without exposing confidential information. Use it when the work involves Project selection, Case-study structure, Confidentiality-safe storytelling.

  1. Whether each claim describes a responsibility or a measurable outcome with the author's actual scope.
  2. Whether the evidence would survive a reference check by someone who was there.
  3. The gap between the target level's expectations and what the artifact demonstrates.
  4. Whether impact is attributed to the individual, the team, or the system, and which is honest.

Failure modes it recognizes

  • Metrics quoted without a baseline or a denominator, which a reviewer discounts entirely.
  • Team outcomes written in the first person, which fails the first probing question.
  • A packet listing activity rather than the decisions the person owned.
  • Scope inflation that is contradicted by the person's own examples during interview.

Answers it will reject

  • Inventing or rounding metrics to strengthen a claim, which is unrecoverable once challenged.
  • Optimizing for keyword matching rather than for the evidence a reviewer looks for.
  • Treating seniority as tenure rather than as demonstrated scope of judgment.

Decision rules it applies

  • Never state an outcome the person cannot substantiate under questioning.
  • Convert responsibilities into outcomes with a baseline, a change, and the person's specific role.
  • Name the largest credibility gap first; polish is worthless if the evidence is thin.

Evidence it asks for

  • For each claim, ask what a skeptical reviewer would request as proof.
  • Compare the artifact against the published expectations for the target level.
  • Rehearse the two questions most likely to expose an overstated claim.

The method inside

  1. Establish what is actually true about project selection from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind case-study structure rather than restating the symptom.
  3. Choose the smallest defensible change for confidentiality-safe storytelling, weighing impact, confidence, effort, and reversibility.
  4. Check clarity, credibility, and screening relevance

Deliverables

  • Project selection assessment
  • Case-study structure decision and action plan
  • Confidentiality-safe storytelling verification checklist

Evidence requirements

  • Current resume or career artifact
  • Target role and job description
  • Verified scope, outcomes, and metrics

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Help me choose and structure three portfolio projects for staff-level platform engineering roles without revealing employer-sensitive details.

Expected output

Choose one architecture decision, one operational recovery, and one leverage/tooling project. For each, preserve the constraint, decision, trade-off, and measurable result while replacing proprietary identifiers and sensitive scale figures...

Boundaries and compatibility

Ideal for

  • Project selection: produce a decision or artifact grounded in supplied evidence.
  • Case-study structure: produce a decision or artifact grounded in supplied evidence.
  • Confidentiality-safe storytelling: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Inventing employers, metrics, projects, or credentials
  • Guaranteeing interviews or hiring outcomes

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.