Profile readme vp

Skill VectorPeak/vectorpeak-agent-skills/dev-skills/profile-readme-vp

A structured collection of reusable Agent and Codex skills for software engineering, knowledge management, and professional workflow automation.

Install

npx -y skills add VectorPeak/vectorpeak-agent-skills --skill profile-readme-vp

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Trigger and verify VectorPeak's personal GitHub profile README automation. Use when the user asks to manually run, rerun, test, check, or validate the VectorPeak/VectorPeak profile README GitHub Actions workflow, especially the Update profile README workflow or update-profile.yml.

SKILL.md

4.0 KB, as published. Nobody here has run it

Profile README VP

Use this skill as a thin operator guide for the remote GitHub Actions workflow that regenerates VectorPeak's profile README. Do not generate the README locally from this skill.

Source of Truth

Skill repository: VectorPeak/vectorpeak-agent-skills
Target repository: VectorPeak/VectorPeak
Default branch: main
Workflow file: .github/workflows/update-profile.yml
Workflow name: Update profile README
Automation branch: automation/update-profile-readme
Expected PR title when README changes: chore: update profile README

The README generation, GitHub fact collection, translation, project classification, contribution classification, star formatting, PR override handling, and pull request reuse logic all live in VectorPeak/VectorPeak. Do not copy or recreate that logic in this skill.

Preflight

Confirm GitHub CLI access before triggering:

gh auth status
gh workflow list --repo VectorPeak/VectorPeak

If Update profile README or update-profile.yml is not listed, stop and report that the remote workflow name or file path may have changed.

Manual Trigger

Prefer GitHub CLI when available:

gh workflow run update-profile.yml --repo VectorPeak/VectorPeak --ref main

If using the GitHub web UI:

Open VectorPeak/VectorPeak.
Go to Actions.
Select Update profile README.
Choose Run workflow.
Select branch main.
Start the run.

Verification

After triggering, verify the run instead of assuming success:

gh run list --repo VectorPeak/VectorPeak --workflow update-profile.yml --event workflow_dispatch --limit 5

Watch the selected run:

gh run watch <run-id> --repo VectorPeak/VectorPeak
gh run view <run-id> --repo VectorPeak/VectorPeak --log

Success means:

The run finishes with completed / success.
If generated README content changed, the workflow pushes automation/update-profile-readme and creates or updates a PR titled chore: update profile README.
If generated content did not change, the workflow exits successfully without opening a noisy PR.

Required Remote Configuration

The remote workflow is expected to own these settings:

Permissions: contents: write and pull-requests: write
Secret: WORKFLOW_PUSH_PAT for checkout, GitHub fact collection, branch push, and PR create/update
Secret: DASHSCOPE_API_KEY for translation
Translation model: PROFILE_TRANSLATION_MODEL=qwen-plus
Schedule: 17 23 * * *, which is 07:17 Beijing time

If a run fails because one of these is missing, report the missing remote configuration and do not patch README generation logic inside this skill.

Failure Handling

If gh auth status fails, ask the user to authenticate or switch to an account with access to VectorPeak/VectorPeak.
If the workflow is missing, inspect VectorPeak/VectorPeak for a renamed workflow before changing this skill.
If the run fails in generation, translation, branch push, or PR creation, fix the workflow or scripts in VectorPeak/VectorPeak.
If the automation PR has conflicts, resolve the PR or automation branch in VectorPeak/VectorPeak; keep this skill unchanged unless the trigger procedure itself is outdated.
If profile content is wrong, update the source data or generation logic in VectorPeak/VectorPeak, then trigger the workflow again.

Boundaries

Do not add local README renderer scripts, sample profile data, GitHub fact collectors, or contribution taxonomy tables to this skill. Keep it as a durable trigger-and-verify guide so there is only one implementation of profile generation.

When the user asks to change profile content, first make the change in VectorPeak/VectorPeak, then use this skill to trigger and verify the remote workflow.