adminprojects/portable-identity-document-template-OPEN
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

added

Browse Source
This commit is contained in:
eddiesoehnel 2026-06-16 13:36:52 -06:00
parent a73f333eae
commit e0359e120c
3 changed files with 341 additions and 31 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

52
README.md
View File

@ -57,6 +57,7 @@ This repository contains the core materials for creating and maintaining a PID.
- [PID-template.md](PID-template.md): the main PID template. Start here to understand the sections your PID should include.
- [skills/PID-initial-creation-skill.md](skills/PID-initial-creation-skill.md): an AI-agent skill for turning your existing materials into a first PID draft. Use this skill to have AI create your PID for you.
- [skills/PID-update-maintenance-skill.md](skills/PID-update-maintenance-skill.md): an AI-agent skill for reviewing your recent activity and drafting updates to keep your PID fresh. Use this skill to have AI maintain your PID for you.
- [skills/PID-update-maintenance-skill-user-variables.md](skills/PID-update-maintenance-skill-user-variables.md): a user-owned companion configuration file for the maintenance skill. Put your PID path, approved source locations, privacy rules, output folders, section preferences, and user-specific workflow adjustments here instead of editing the main maintenance skill.
- [PID-maturity-model-roadmap.md](PID-maturity-model-roadmap.md): a roadmap for moving from a simple PID document toward a structured, agent-native, and eventually agent-maintained identity layer.
## Start Here
@ -156,7 +157,21 @@ A PID should be a living document. If it goes stale, its usefulness declines.
Run [skills/PID-update-maintenance-skill.md](skills/PID-update-maintenance-skill.md) regularly, preferably weekly.
That skill is designed to help an AI agent review user-approved sources such as:
Before running it, fill out or maintain [skills/PID-update-maintenance-skill-user-variables.md](skills/PID-update-maintenance-skill-user-variables.md). This companion file is where your personal variables live:
- current PID location and format
- default review timeframe
- review draft and receipt output folders
- approved local, cloud, email, calendar, repository, transcript, database, and publishing sources
- sources that are not authorized
- privacy boundaries
- update goals
- section, voice, evidence, and receipt preferences
- user-specific adjustments to how the maintenance skill should behave
Keep those variables outside the main skill. The main maintenance skill may be improved over time, and your user variables file should persist across those updates.
The maintenance skill is designed to help an AI agent review user-approved sources such as:
- local project folders
- notes and documents
@ -172,11 +187,14 @@ That skill is designed to help an AI agent review user-approved sources such as:
The maintenance skill follows a review-first process:
1. You provide your current PID and approved sources.
2. The agent scans the selected timeframe, usually the last 7 days.
3. The agent creates a local Markdown review draft.
4. You edit, delete, correct, or add context.
5. Only after approval does the agent append updates to your PID.
1. You fill out or update `PID-update-maintenance-skill-user-variables.md`.
2. You ask the agent to run the maintenance skill.
3. The agent reads the user variables file, then asks only for missing or ambiguous values.
4. The agent confirms the current PID, timeframe, approved sources, output location, and privacy boundaries.
5. The agent scans the selected timeframe, usually the last 7 days unless your variables specify otherwise.
6. The agent creates a local Markdown review draft.
7. You edit, delete, correct, or add context.
8. Only after approval does the agent append updates to your PID.
Suggested weekly prompt:
@ -187,13 +205,21 @@ My PID is here: [path or link]
Review this timeframe: last 7 days
Save the review draft here: [folder]
Approved sources:
- [folders]
- [email labels or accounts]
- [calendar range]
- [meeting transcript folders]
- [CSV/JSON/database exports]
- [other sources]
Use my companion variables file beside the skill:
skills/PID-update-maintenance-skill-user-variables.md
Approved sources, with exact locations or access scopes:
- Local PC folders: [full paths]
- Cloud files/folders/connectors: [Google Drive/OneDrive/Dropbox/etc. paths, links, or connector scopes]
- Email accounts or labels: [account + labels/queries]
- Calendar range/account: [calendar + date range]
- Meeting transcript folders or recording exports: [full paths or links]
- Git repositories, including histories: [full paths or remotes]
- CSV/JSON/database/spreadsheet exports: [full paths or links]
- Publishing/content/social/newsletter sources: [paths, exports, or accounts]
- Other sources: [exact source and access method]
Do not assume the PID repo or the folder containing my PID is an approved source unless I list it above or include it in my user variables file.
Privacy boundaries:
- never include [items]

238
skills/PID-update-maintenance-skill-user-variables.md Normal file
View File

@ -0,0 +1,238 @@
# PID Update Maintenance Skill User Variables
## Purpose
This is the user-owned companion configuration file for `PID-update-maintenance-skill.md`.
Keep user-specific variables here so the main skill can improve over time without overwriting a user's local paths, source permissions, privacy rules, output preferences, or workflow adjustments.
Agents using the main PID update maintenance skill should read this file first when it exists beside the main skill. Treat this file as user-controlled configuration and preference context, not as a replacement for the main workflow or validation gates.
## How To Use
1. Copy this file beside `PID-update-maintenance-skill.md`.
2. Fill in only the fields that apply.
3. Keep private values in your own local copy when needed.
4. When the main skill is updated, preserve this file unless the user explicitly asks to replace it.
5. If a field conflicts with the main skill, follow the stricter privacy/review rule unless the user gives explicit approval.
## Current PID
- PID location or link:
- PID format: Markdown / Google Doc / Word / OneDrive / PDF / website / repo / other
- Canonical source of truth:
- Direct editing allowed: yes / no / ask each time
- Preferred update method: direct edit / copy-ready Markdown / review draft only
## Default Timeframe
- Default review window: last 7 days
- Alternative recurring window:
- Date/timezone preference:
## Output Locations
- Review draft folder: portable-identity-document-template-OPEN\review-drafts
- Review draft filename pattern: `PID-update-review-draft-[YYYY-MM-DD].md`
- Source map folder:
- Open questions folder: portable-identity-document-template-OPEN\skills-recepits
- Run receipt folder: portable-identity-document-template-OPEN\skills-recepits
- Run receipt filename pattern: `PID-update-run-receipt-[YYYY-MM-DD].md`
## Approved Data Sources
List every source the agent may review. Do not rely on the main skill to infer these.
### Local PC Folders
-
### Cloud File Locations Or Connectors
-
### Git Repositories
-
### Email Accounts, Labels, Or Queries
-
### Calendar Accounts Or Ranges
-
### Meeting Transcript Or Recording Export Locations
-
### Chat Logs Or Collaboration Tool Exports
-
### CRM, Database, CSV, JSON, Or Spreadsheet Exports
-
### Browser Bookmarks, Reading Lists, Or History
-
### Social, Newsletter, Publishing, Portfolio, Or Website Sources
-
### Photos, Screenshots, Design Files, Or Media Metadata
-
### Learning Logs, Courses, Books, Papers, Or Saved Articles
-
### Financial, Sales, Support, Product, Or Analytics Exports
-
### Other Sources
-
## Sources Not Authorized
List paths, accounts, connectors, labels, folders, or source types that must not be scanned.
-
## Privacy Boundaries
### Never Include
-
### Summarize But Do Not Name
-
### Ask Before Including
-
### Safe To Include
-
## Update Goals
- What should the PID become easier to find for?
- What people, opportunities, markets, or matches matter right now?
- What current needs should be especially visible?
- What current offers or assets should be especially visible?
- What should AI systems not misunderstand about the user?
## Section Preferences
Use this area to tune how the main skill maps findings into the user's PID.
- Sections to prioritize:
- Sections to keep brief:
- Sections that should usually remain private:
- Sections that should receive detailed evidence:
- Preferred section names if different from the template:
- Custom PID sections to preserve:
## Voice And Style Preferences
- Preferred tone:
- Avoid these phrases or framings:
- Use first person / third person:
- Detail level:
- Public-facing wording preference:
## Review And Approval Rules
- Always create review draft before PID update: yes
- Require user approval before direct PID edit: yes
- Require separate approval before public publication: yes
- Require separate approval before including inferred needs: yes / no / ask
- Require separate approval before including inferred offers: yes / no / ask
- Require separate approval before including personal, health, family, financial, legal, client, or private operational details: yes
## Skill Adjustments For This User
Use this section for user-specific adjustments to the main skill. These are intended to tune behavior without editing the main skill.
Examples:
- Prefer detailed `WHAT I HAVE` extraction over weekly activity summaries.
- Treat publication receipts as high-confidence evidence of shipped work.
- Treat proposals and outreach as review-only until user confirms public status.
- Generalize edge infrastructure and private operational details.
User-specific adjustments:
-
## Source Priority Rules
Optional guidance for scanning broad source roots.
- Prioritize:
- Deprioritize:
- Skip generated/cache folders:
- Treat these folders as public-safe:
- Treat these folders as private/review-only:
## Evidence Rules
- Evidence detail level:
- Acceptable evidence types:
- Require source paths in review draft: yes / no
- Require confidence labels: yes
- Require privacy labels: yes
- Treat unsupported inferences as questions: yes
## Run Receipt Preferences
- Always create run receipt: yes / no / serious runs only
- Receipt folder:
- Include command/tool log: yes / no
- Include skipped sources: yes
- Include privacy decisions: yes
- Include ratchet lessons: yes
## Ratchet / Future Skill Improvement Notes
Use this section to store recurring lessons that should improve future runs.
-
## Example Filled Minimal Configuration
```md
## Current PID
- PID location or link: C:\path\to\my-PID.md
- PID format: Markdown
- Direct editing allowed: ask each time
## Default Timeframe
- Default review window: last 10 days
## Approved Data Sources
### Local PC Folders
- C:\Users\me\My Drive
- C:\projects
## Privacy Boundaries
### Never Include
- credentials, private keys, account numbers, raw customer data
### Ask Before Including
- client details, family details, health details, private infrastructure details
## Skill Adjustments For This User
- Be detailed in `WHAT I HAVE`.
- Include small scripts, workflows, templates, receipts, and reusable processes.
- Generalize private operational details.
```

82
skills/PID-update-maintenance-skill.md
View File

@ -13,12 +13,37 @@ People will not manually maintain rich PID profiles indefinitely. Each week they
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.
## User Variables Companion
Before running this skill, check for a companion file named `PID-update-maintenance-skill-user-variables.md` in the same folder as this skill.
Use that file for user-owned variables and preferences such as:
- current PID location and format
- default timeframe
- review draft and receipt output locations
- approved source paths, cloud locations, connectors, labels, repositories, and export files
- sources that are not authorized
- privacy boundaries
- update goals
- section preferences
- voice/style preferences
- review and approval rules
- user-specific skill adjustments
- source priority rules
- evidence and receipt preferences
The companion file is intentionally separate from the main skill so users can customize the maintenance workflow without editing the core skill. The main skill may be updated by maintainers over time; the user variables file should persist across main-skill updates.
Treat the companion file as configuration, not as permission to bypass the main contract. If the companion file conflicts with the main skill, follow the stricter privacy, source-boundary, evidence, and review-gate rule unless the user explicitly approves otherwise.
## 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 look for and read `PID-update-maintenance-skill-user-variables.md` beside this skill when present, then use it to prefill intake, defaults, source lists, privacy boundaries, and user-specific adjustments.
- It will ask the user to explicitly list every data source location, account, connector, export, folder, repository, and cloud document set authorized for review; the PID repo or PID file location is never assumed to be the activity source unless the user says so.
- 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.
@ -48,6 +73,8 @@ This skill requires:
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.
If `PID-update-maintenance-skill-user-variables.md` exists, read it before asking intake questions. Use it to reduce repeated questions, but still ask the user to confirm missing, stale, risky, or ambiguous variables before scanning sources or editing a PID.
## Ensures
Before finishing, this skill ensures:
@ -107,6 +134,8 @@ If the host cannot provide the primitive needed for a requested source or output
At the beginning, ask the user to provide or confirm the following. Keep the intake concise if the user has already supplied some answers.
If `PID-update-maintenance-skill-user-variables.md` exists, prefill this checklist from it and ask the user only for missing or ambiguous values.
```md
# PID Update Intake
@ -124,9 +153,12 @@ At the beginning, ask the user to provide or confirm the following. Keep the int
- Preferred draft filename:
## Approved Data Sources
- Local project folders:
List every authorized source explicitly. Do not assume the PID repo, the folder containing the PID, the current workspace, or recently modified nearby files are approved activity sources unless the user names them. Ask for exact local paths, cloud locations, connector scopes, account labels, export files, repositories, or date-bounded queries for each source category.
- Local PC folders and exact paths:
- Notes folders:
- Documents folders:
- Cloud file locations or connectors (Google Drive, OneDrive, Dropbox, iCloud, SharePoint, etc.):
- Downloads or exports:
- Git repositories, including histories:
- Email accounts or labels:
@ -260,13 +292,14 @@ Prefer concrete, grounded language over generic praise.
### Phase 1: Intake And Permission
1. Ask for the current PID path/link and format.
2. Ask for the timeframe. Use the last 7 days if the user says weekly or gives no range.
3. Ask which source categories are approved and where to find them.
4. Ask for privacy boundaries.
5. Ask where to save the local review draft.
1. Look for `PID-update-maintenance-skill-user-variables.md` beside this skill. If present, read it and extract defaults, approved sources, privacy boundaries, output preferences, and user-specific adjustments.
2. Ask for or confirm the current PID path/link and format.
3. Ask for or confirm the timeframe. Use the user variables default when present; otherwise use the last 7 days if the user says weekly or gives no range.
4. Ask the user to list or confirm every approved source location and access method, including local PC paths, cloud folders/connectors, email accounts or labels, calendars, meeting transcript folders, chat exports, repositories, databases, spreadsheets, and publishing/content systems. Do not infer sources from the PID path, current repo, cwd, or neighboring folders.
5. Ask for or confirm privacy boundaries.
6. Ask where to save the local review draft if not specified in user variables.
Stop if the user has not authorized any source review.
Stop if the user has not authorized at least one explicit source location, connector scope, account label, export file, repository, or bounded query to review.
### Phase 2: Read The Current PID
@ -282,10 +315,10 @@ Completion criteria:
### Phase 3: Source Inventory
1. List each approved source.
1. List each explicit approved source, including path/account/connector/query, source category, date range, and scan limits.
2. Record access method, date range, and scan limits.
3. Prefer metadata and targeted searches before reading large corpora.
4. Do not read sources outside the user's approved categories.
4. Do not read sources outside the user's explicitly listed locations, connectors, accounts, repositories, exports, or bounded queries, even if they are near the PID file or appear recently modified.
5. Track unreadable or skipped sources in the run receipt.
Completion criteria:
@ -465,7 +498,7 @@ Use validation tiers so the agent does not confuse a quick structural check with
Run every time:
- intake captured PID location, timeframe, approved sources, and privacy boundaries
- intake captured PID location, timeframe, privacy boundaries, and at least one explicit approved source location/account/connector/export/repository/query; PID folder/source assumptions are not acceptable
- review draft exists before any PID update
- every proposed update has a PID section placement
- every fact has evidence
@ -616,6 +649,9 @@ Do not:
- update the PID before the user reviews the Markdown draft
- scan sources the user did not authorize
- treat the user variables companion file as permission to scan sources not listed in it or explicitly confirmed by the user
- overwrite or delete `PID-update-maintenance-skill-user-variables.md` when updating the main skill unless the user explicitly asks
- require users to edit the main skill for their own paths, preferences, or workflow tuning
- treat all recent files as meaningful
- dump raw private notes into the PID
- publish sensitive details because they were found in a source
@ -634,6 +670,8 @@ Do not:
When this skill is updated, verify:
- frontmatter contains only `name` and `description`
- `PID-update-maintenance-skill-user-variables.md` remains separate from the main skill and is not overwritten by default
- instructions still tell agents to read the user variables companion file before intake when it exists
- PID section lists still match `PID-template.md`
- output filenames still match the README and user prompts
- validation sections still require structural, evidence, privacy, quality, and receipt checks
@ -803,13 +841,21 @@ 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]
If present, use my companion variables file beside the skill:
PID-update-maintenance-skill-user-variables.md
Approved sources, with exact locations or access scopes:
- Local PC folders: [full paths]
- Cloud files/folders/connectors: [Google Drive/OneDrive/Dropbox/etc. paths, links, or connector scopes]
- Email accounts or labels: [account + labels/queries]
- Calendar range/account: [calendar + date range]
- Meeting transcript folders or recording exports: [full paths or links]
- Git repositories, including histories: [full paths or remotes]
- CSV/JSON/database/spreadsheet exports: [full paths or links]
- Publishing/content/social/newsletter sources: [paths, exports, or accounts]
- Other sources: [exact source and access method]
Do not assume the PID repo or the folder containing my PID is an approved source unless I list it above.
Privacy boundaries:
- never include [items]