nanaagyei/noetherkin / skills/resume-evidence
resume-evidence
VerifiedDerive truthful resume evidence from verified Noetherkin records with assistance and simulation qualifiers. Use for evidence inventories and draft bullets, not credentials or invented impact.
references/contract-resume-evidence.md
View on GitHub# resume-evidence contract
Version 2.0. Inherits [shared conventions](contract-README.md).
## Purpose
Help the learner derive accurate resume-ready statements from verified evidence without creating credentials or inflating simulation into employment experience.
## Trigger Conditions
The learner requests a resume evidence inventory or wording grounded in apprenticeship records.
## Preconditions
Learner-authorized access to relevant verified records and artifacts. The learner owns the final representation.
## Inputs and State
Read current unsuperseded evidence, supporting artifacts, assistance, project provenance, and validity status. Produce a learner-reviewed draft or the optional derived `evidence/resume-evidence.md`; it is not canonical evidence.
## Allowed and Forbidden Actions
Trace every claim to support, quantify only measured results, disclose simulation where material and attach it to what was actually simulated: software the learner wrote from a forge specification is real, learner-authored software, while the team, reviews and process around it were simulated, and separate contribution from assistance. The action verb must not exceed the evidenced contribution: independent test design cannot be rewritten as updating, implementing or correcting code. If implementation authorship or assistance is unknown, code is context only (“tested revision B”), not a learner contribution, unless marked `[VERIFY]`. Do not invent employers, users, production impact, upstream acceptance, credentials, or revive stale/refuted claims.
## Required Output
Claim, evidence IDs/artifacts, truthful scope, assistance/simulation qualifier, verification status, and `[VERIFY]` for any unsupported wording.
## Failure and Repeat Behavior
No verified support means no affirmative bullet. Regenerate when cited heads or availability change; never silently preserve invalidated claims.
## Handoffs
Team-lead verifies underlying evidence; performance-review may supply context but is not itself proof of engineering behavior.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |