associate-artifact-search

Associate Artifact Search

Gather an associate's work products across Jira, GitHub, GitLab, Google Drive, and Gmail for a given time window. Each platform is queried by a dedicated script that outputs structured JSON; the skill then produces a markdown highlight summary.

Step 0 — Look up People note defaults

If the user provided a person name, attempt to look up their People note for pre-populated defaults.

1. Resolve the Obsidian vault root:

   cat ~/Library/Application\ Support/obsidian/obsidian.json
   

   Parse JSON to find the vault with "open": true or highest ts.

2. Read <vault_root>/PEOPLE/<person name>.md. If the file doesn't exist, skip to Step 1 (fully manual entry).

3. Parse YAML frontmatter and extract:

   • GitHub username: From the social list, find a URL matching https://github.com/<user> and extract <user>
   • GitLab username: From the social list, find a URL matching https://gitlab.com/<user> or https://gitlab.cee.redhat.com/<user> and extract <user>. If no GitLab URL is in the social list but the email is @redhat.com, derive the GitLab username from the email prefix (e.g., [email protected] → jbalunas, defaulting to https://gitlab.cee.redhat.com/jbalunas)
   • Email: Read the mail field (Red Hat contacts) or email field (external contacts)
   • Jira identity: Use the same email value (search_jira.py resolves email → account ID)
   • Google email: Use the same email value

4. Pass any discovered values as defaults to Step 1.

Step 1 — Gather inputs

Pre-populated defaults: When Step 0 found a People note with platform identities, add a recommended first option to each relevant question below. For example, if GitHub username vkareh was extracted from the People note, Q2 should have "Use vkareh (from People note) (Recommended)" as the first option. If a field has no default from Step 0, leave that question unchanged. Original options always remain available for override.