github-profile-proof-updater
/github-profile-proof-updater
Refresh and verify a GitHub profile or public proof layer. Use when the user wants to update GitHub profile visuals, replace README assets while preserving paths, audit profile image references, validate live GitHub rendering, prepare LinkedIn/X proof copy, or document a profile-refresh proof trail.
- Author
- jqaisystems ↗
- Repository
- jqai-ai-skills ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Refresh and verify a GitHub profile or public proof layer. Use when the user wants to update GitHub profile visuals, replace README assets while preserving paths, audit profile image references, validate live GitHub rendering, prepare LinkedIn/X proof copy, or document a profile-refresh proof trail.
Original author description
Refresh and verify a GitHub profile or public proof layer. Use when the user wants to update GitHub profile visuals, replace README assets while preserving paths, audit profile image references, validate live GitHub rendering, prepare LinkedIn/X proof copy, or document a profile-refresh proof trail.
How it works
- Overview
- Workflow
- Public Safety Rules
- Social Proof Handoff
- Output Format
SKILL.md preview
--- name: github-profile-proof-updater description: Refresh and verify a GitHub profile or public proof layer. Use when the user wants to update GitHub profile visuals, replace README assets while preserving paths, audit profile image references, validate live GitHub rendering, prepare LinkedIn/X proof copy, or document a profile-refresh proof trail. --- # GitHub Profile Proof Updater ## Overview Use this skill to turn a GitHub profile or proof-layer refresh into a repeatable, public-safe workflow: update visuals, preserve working README paths, verify the live page, and create the social/proof trail that explains the update. Do not publish, commit, push, upload, or post externally unless the user explicitly asks for that action. ## Workflow 1. Confirm the target repo and the source asset folder. 2. Inspect the current repo state: - `git status --short` - README image references - target asset filenames and dimensions 3. Preserve existing public paths unless the user asks for a rename in README. - Prefer replacing assets under the old filenames. - Keep known-good hero images unchanged when the user says the hero is already good. 4. Copy or replace only the intended assets. 5. Validate the changed media: - destination files exist - images are readable - dimensions/aspect ratios are plausible for the README layout 6. Re-check README references. - Edit README only if an image path is broken, missing, or intentionally changing. 7. Review the diff and repo status. - Never use broad staging until the changed files are understood. - Prefer staging named files only. 8. If the user asks to commit/push, commit with a focused message and push the current branch. 9. Verify the live GitHub profile or public repo page after push. - Check that all updated visuals render. - Confirm the unchanged hero remains correct. - Capture any broken image, stale cache, or layout issue. 10. Create or update the proof trail: - public GitHub links - commit links or hashes - asset summary - LinkedIn/X post links when available - follow-up checklist ## Public Safety Rules - Do not include local machine paths, private vault structure, raw prompts, logs, credentials, browser cookies, private repo names, account identifiers, or client data in public files. - Screenshots must not reveal private tabs, emails, analytics, billing, dashboards, file paths, or account menus. - Social copy should describe outcomes and workflow categories, not private implementation details. - If a public artifact is being prepared, apply the `github-safe-publisher` rules and run its scanner when available. ## Social Proof Handoff When the user wants LinkedIn or X copy for the refresh: - Lead with the public proof angle. - Keep LinkedIn reflective and explanatory. - Keep X shorter, with one idea per post. - Add alt text for every image. - Put related X posts into a thread, not scattered comments. - Track published links in a proof trail or engagement tracker. ## Output Format Return: 1. Verdict: `BLOCK`, `REVIEW`, or `READY`. 2. Target repo and files changed. 3. Validation performed. 4. Live verification result, if applicable. 5. Proof/social artifacts created or updated. 6. Next recommended action.
Files in this package (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named github-profile-proof-updater.
Database snapshot: 13.11.2026 · package version 8398af97797c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90github-profile
Create or update an animated, living GitHub profile README with github-profile-kit (one profile.toml, a GitHub Action, live stats, a skyline with real weather). Use when someone asks to make, pimp, redesign or refresh a GitHub profile, or when an agent with its own GitHub… - 100social-campaign-proof-tracker
Plan, document, and follow up on public proof campaigns across LinkedIn, X, GitHub, websites, and videos. Use when the user wants carousel or thread copy, alt text, post/video captions, public link tracking, reply banks, engagement review, or a campaign proof trail after publishing project work. - 100github-presence
When the user wants to optimize their GitHub profile, README, or project discoverability. Trigger phrases include "GitHub README," "README optimization," "GitHub profile," "GitHub stars," "GitHub discoverability," "awesome lists," or "GitHub marketing. - 100github-presence
When the user wants to optimize their GitHub profile, README, or project discoverability. Trigger phrases include "GitHub README," "README optimization," "GitHub profile," "GitHub stars," "GitHub discoverability," "awesome lists," or "GitHub marketing. - 100github-profile-readme-optimization-showcase
Use this skill when designing a compelling, developer-centric GitHub profile README highlighting top projects, stats, and skills. - 95Brand
The principal brand integrity system: sweeps and refreshes brand/focus messaging across every public surface (GitHub profile README, blog, company site, marketing site, repo READMEs, LinkedIn/X/YouTube bios) to current focus, names, star counts, and flagship writing, from one…