description: Maintain and update an existing Portable Identity Document (PID) by scanning user-approved local files, emails, transcripts, calendars, databases, exports, and other digital activity over a chosen timeframe. Use this skill when a user wants an AI agent to discover recent accomplishments, learnings, projects, relationships, needs, assets, proof of work, insights, and other signals; draft a reviewable PID update file; incorporate user edits; and append approved updates to the user's PID in Google Docs, Microsoft Word/OneDrive, Markdown, PDF/source file, repository, or another accessible format.
---
# PID Update Maintenance Skill
## Purpose
Help a user keep an existing Portable Identity Document current with minimal manual effort.
People will not manually maintain rich PID profiles indefinitely. Each week they learn things, complete projects, build relationships, create content, solve problems, make decisions, discover tools, attend meetings, and develop new needs or offers that may be valuable signals to others. This skill delegates the ongoing observation, summarization, categorization, and update-drafting work to an AI agent while preserving human review and control.
The agent should look for meaningful change across user-approved sources, draft a local Markdown review file organized by the user's current PID structure, invite the user to edit that draft, learn from those edits when asked, and only then append approved updates to the PID.
## Contract
This skill guarantees:
- It will ask for the user's current PID location and format before attempting updates.
- It will ask which data sources the user authorizes for review.
- It will respect the requested timeframe, defaulting to the last 7 days when no timeframe is provided.
- It will create a local Markdown draft before changing the PID.
- It will organize findings according to the user's actual PID structure when readable, falling back to the standard PID template sections when needed.
- It will distinguish sourced facts, reasonable inferences, and user-review questions.
- It will surface small but meaningful signals, not only major achievements.
- It will preserve privacy and avoid publishing sensitive data unless explicitly approved.
- It will not update, overwrite, publish, email, or share the PID without user confirmation after review.
- It will produce a run receipt documenting inputs, outputs, validations, and unresolved risks.
- It will ratchet lessons from user edits into improved instructions when the user asks the agent to adjust the skill.
## Skill Shape
`system`
This skill coordinates intake, source review, signal extraction, categorization, user review, final PID update, validation, and skill-improvement feedback.
## Requires
This skill requires:
- A user-provided link or path to the current PID.
- User authorization for each source category reviewed.
- A date range or timeframe, or permission to use the default weekly window.
- Ability to read at least one source of recent activity.
- Ability to create a local Markdown draft for review.
- Explicit user approval before modifying the PID.
If the PID is inaccessible, ask the user for an export, local copy, pasted text, or connector access. Do not infer the PID structure from memory alone.
## Ensures
Before finishing, this skill ensures:
- A review draft exists before any PID update.
- The user has either approved the draft, or the PID remains unchanged.
- Approved updates are placed into the correct PID sections.
- Rejected, private, or low-confidence items are excluded or converted into questions.
- The final response clearly states whether the PID was updated or is still awaiting review.
## Capabilities
Required host capabilities:
- CLI tools: useful for local file discovery, date filtering, Git history, and source inventory.
- MCP/connectors: optional but recommended for Gmail, Google Calendar, Google Drive, Google Docs, OneDrive, databases, and other external systems.
- Browser access: optional; use only for user-approved web-accessible PIDs or publication checks.
- Filesystem access: required for local source scanning and Markdown draft output unless the user works entirely through connectors.
- Network access: optional; use only for user-approved cloud documents, repositories, or web sources.
- Subagent support: optional for large source reviews or reviewer-panel passes.
- Document/spreadsheet/PDF support: useful when the PID or sources are Word, Sheets, Excel, PDF, or exported reports.
If a required capability is unavailable, stop or narrow the workflow. Do not pretend to have reviewed inaccessible sources.
## State Scope
`project`
Persistent writes:
- local review draft
- optional source map
- optional open questions file
- optional run receipt
- approved PID update when the user confirms publication
Do not write long-term user memory or update the skill itself unless the user explicitly asks the agent to preserve a recurring preference or adjust the skill.
## Host Primitive Adapter
Map abstract workflow needs to available host actions:
Agent response to human when PID update review draft is complete: This is a draft for your review before anything is added to your Portable Identity Document (PID).
- add missing context, links, examples, names, or proof
- mark private items that should be removed or generalized
- strengthen anything that feels too vague or too narrow
After you edit this draft, ask the agent to continue from your revised file and update your PID.
If your edits reveal a recurring preference, missing category, privacy rule, source type, or better way to describe your work, ask the agent to adjust the PID update maintenance skill so future runs improve.
```
## PID Section Mapping
First read the user's current PID and infer its headings. Preserve the user's structure when appending updates.
If the PID cannot be read or has no clear structure, use the standard PID sections:
This list is based on the pid-template.md file. That file may evolve to a different structure. Make sure the user has given the AI access to the latest version of this file.
Ask the user to review and edit the Markdown file. Do not update the PID yet.
Continue only when the user explicitly says the draft is ready, approved, or provides the revised file.
### Phase 8: Incorporate User Edits
1. Read the edited review draft.
2. Treat user edits as authoritative.
3. Remove rejected items.
4. Generalize private items.
5. Strengthen items the user expanded.
6. Identify any preference that should improve future skill runs.
If the user's edits imply a recurring rule, ask whether to update the skill or add that rule to a local preference note.
### Phase 9: Update The PID
Update method depends on format:
- Google Doc: use the Google Drive/Docs connector when available, or prepare copy-ready Markdown.
- Microsoft Word/OneDrive: edit a local `.docx` or prepare copy-ready content for OneDrive when direct connector access is unavailable.
- Markdown: append or merge directly into the appropriate sections.
- PDF: update the source document first when possible; avoid editing the PDF as the canonical source unless the user confirms it is the source of truth.
- Website/repo: update the source Markdown/data files, not only the generated site.
- Unknown or locked format: provide copy-ready approved update text.
Append to existing sections rather than rewriting the entire PID unless the user requests restructuring.
### Phase 10: Validate And Receipt
Before finishing:
1. Re-read the changed PID when possible.
2. Confirm approved updates appear in the intended sections.
3. Confirm rejected/private items were not included.
4. Confirm the Update Log includes the timeframe and date.
5. Confirm no unsupported inference was promoted to fact.
6. Write or update the run receipt.
## Validation
Structural validation:
- [ ] Current PID was read or fallback limitation was disclosed.
- [ ] Review draft was created before PID update.
- [ ] Draft used the user's PID structure or standard fallback.
- [ ] Every proposed update has section placement.
- [ ] Final PID update only happened after user approval.
Evidence validation:
- [ ] Every fact has source evidence.
- [ ] Every inference is labeled.
- [ ] Every low-confidence item is either excluded or turned into a question.
- [ ] Source limits and skipped sources are recorded.
Privacy validation:
- [ ] Privacy boundaries were collected.
- [ ] Sensitive identifiers were excluded or generalized.
- [ ] Private client, employer, family, health, legal, financial, or confidential project details were not published without approval.
- [ ] Draft includes privacy notes where needed.
Quality validation:
- [ ] Small learnings, improvements, and aha moments were considered.
- [ ] Needs and offers were both reviewed.
- [ ] Possible match implications were surfaced.
- [ ] Generic language was replaced with concrete signals where possible.
- [ ] User edits were incorporated faithfully.
## Test Surface
This skill can be tested through:
- Static checks: required sections exist in the draft; draft header exists; run receipt exists.
- Invariant checks: no PID update before review approval; every proposed fact has evidence; every inference is labeled.
Use the PID Update Maintenance Skill to update my Portable Identity Document.
My PID is here: [path or link]
Review this timeframe: [last 7 days / dates]
Save the review draft here: [folder]
Approved sources:
- [folders]
- [email labels or accounts]
- [calendar range]
- [meeting transcript folders]
- [CSV/JSON/database exports]
- [other sources]
Privacy boundaries:
- never include [items]
- generalize [items]
- ask before including [items]
First create a local Markdown review draft organized by my PID sections. Do not update the PID until I review and approve the draft.
```
## One-Sentence Version
Scan user-approved recent activity, extract grounded identity signals, draft them into the user's PID structure for human review, then append approved updates so the PID stays fresh, specific, and useful for AI-native matching.
