All profiles

AI Native Score

Alex Kim

Product engineer

12 dimensions reviewed

The shape of a workflow

44/60

Strong in MCP, skills, context, and evaluation.

A builder who checks the result, questions the evaluation, and leaves unfinished work honestly unfinished. The next step is carrying that rigor across sessions.

How the score works
AI codingMCPSkillsHooksContextMemoryLoopsGraphsMulti-agentIsolationRoutingEval

0 at the center · 5 at the edge

The full picture

Twelve dimensions, one workflow.

What the score reflects, one practice at a time.

Each scored out of 5
01

AI Coding Tools

4/5

From asking about code to implementing and verifying real changes.

Implemented changes and ran tests across separate tasks. The final output and last round of changes were not fully verified in a second independent task.

02

MCP

5/5

Using connected tools and checking what actually happened.

Updated a spreadsheet, read the same cells again, and compared the saved values while checking that existing rows were preserved.

03

Skills

5/5

Applying reusable procedures and improving them through use.

Applied a skill, reviewed and revised its procedure, then checked the outcome in another execution. Failed results remained marked as failed.

04

Hooks

1/5

Running automatic checks at the moments that matter.

Stop hooks executed and recorded timing and errors. Their checking, blocking, and exception-handling effects were not established.

05

Context Engineering

5/5

Giving an agent the right information, and correcting it when needed.

Compared an evaluator’s interpretation with the original material, corrected a mistaken context judgment, and carried that correction into the final report.

06

Memory Engineering

1/5

Carrying useful knowledge across sessions and applying it again.

Saved rules and a direction for future work. No verified link showed the same material being applied in a different session.

07

Loop Engineering

4/5

Designing feedback, retries, and clear stopping conditions.

Implemented and ran attribution checks, a stop-on-pass rule, and a maximum of two regeneration attempts. Resume behavior across executions was not verified.

08

Graph Engineering

3/5

Connecting stages with explicit inputs, outputs, and dependencies.

Connected task material to generated notes, evaluation results, and a final aggregation. Input checks and dependency recovery across the whole flow were not established.

09

Multi-Agent

4/5

Dividing work between agents and checking the combined result.

Separated writing and evaluation roles, integrated returned results, and resolved conflicting judgments against original material. Complete coverage checks were not verified.

10

Worktree / Isolation

4/5

Keeping work separate and delivering it without unrelated changes.

Edited in a separate worktree, reviewed the change scope, and delivered a PR. Preservation of the original checkout and final delivery consistency were not fully verified.

11

Model Routing

3/5

Choosing models for a reason and checking the effect of that choice.

Explicitly assigned a model to evaluation work, with the execution model visible in the records. Comparable quality, cost, or speed evidence was missing.

12

Eval

5/5

Evaluating AI outputs against criteria, then checking the evaluation itself.

Defined AI tasks and success criteria, evaluated multiple executions, corrected grading errors, and retained failed outcomes in the final aggregation.

Keep doing this

Where it comes together.

  1. Checks the evaluator, too

    Revisited a six-result evaluation batch and corrected the final judgments against the source material.

  2. Verifies external changes

    Read back spreadsheet values and checked existing rows instead of stopping at a successful tool response.

  3. Keeps the outcome honest

    Preserved a failed result and delivered it in the requested review state, with its limitations visible.

Try next

Make the next run count.

  1. Close the memory loop

    Retrieve one saved rule in another session, use it in a real decision, and record what happened.

  2. Make a loop resumable

    Persist progress outside the conversation and let a separate execution read it to resume or stop.

  3. Compare model choices

    Run the same evaluation task with two models under the same criteria, then use the result for the next assignment.

Get your own score Explore Maya Chen’s workflow