portable-identity-document-template-OPEN/skills/PID-update-maintenance-skill-user-variables.md

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

## 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.