vp update

Other Community v0.1.1

Skill notes

Invocation Banner

Output this banner as the first thing on every invocation — before questions, work, or any other output: </greeting> <version_check>

Version Update Check (ENH-072)

After displaying the greeting banner, run: If exit code = 1 (update available — new version printed to stdout): Display notice banner before any other output: Replace {latest_version} with stdout from the command, {current} with the installed version, {adapter_id} with the active adapter (claude-code / cursor / antigravity / codex / copilot).

Persona Context Injection (ENH-073)

At skill start, run: Inject the output as ## User Persona context before any task execution. Silent if command unavailable or errors. </persona_context> <adapter id="claude-code">

B. Tool Usage

Use Claude Code tools: Bash (shell), Read (file), Edit + Write (file write/patch), Grep (search), Glob (file patterns), LS, WebSearch, WebFetch, Agent (spawn subagent — multi-level nesting supported) Interactive: AskUserQuestion (deferred — preload via ToolSearch before first call) </adapter>

C. Tool Usage

Use Cursor tools: run_terminal_cmd (shell), read_file (read), edit_file (write/edit), grep_search (search), web_search, codebase_search, list_dir, file_search Interactive: text list fallback (AskQuestion available in Plan Mode only; Agent Mode = text) Subagent: /multitask (user command, single-level only — not a callable tool) MCP limit: 40 tools

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@0-CODE · v0.1.1 · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Dry run (default when automated)

Read output: planned npm command, current version vs latest, ambiguous/global warnings.

02
Step 2: Apply (after user confirms or explicitly requests it)

Or force global:

03
Step 3: Interactive

If the terminal is interactive and no `--yes` flag is present, the CLI may prompt for confirmation before running npm.

04
Step 4: Suggested rollback

Dry-run/update output typically suggests `npm install -g viepilot@<previous>` — keep the previous version from `vp-tools info` in case a rollback is needed. </process> <success_criteria> [ ] Do not run apply in non-interactive mode without `--yes` [ ] Clearly state target (local vs global) when user is in an external project

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.