القائمة
Guide on how to review GSV packages before approval, including source inspection, manifests, capabilities, entrypoints, staged edits, refs, and trust boundaries.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Create or revise reusable GSV agent workflows under skills.d. Use when the user asks to automate, save, teach, repeat, or reuse a workflow, or accepts an offer to preserve a proven workflow for later.
Use extension-provided browser targets to inspect and operate active browser state through the target's advertised filesystem and shell commands.
Guide on how to build and modify GSV packages, including source checkout, app/backend/CLI changes, manifests, validation, staged commits, and syncing.
Use the GSV Manual for questions about GSV's operating model, user workflows, settings, devices, users and agents, packages, automation, integrations, filesystem, desktop, updates, and source/debug orientation.
استنادا إلى تصنيف SOC المهني
| name | gsv-package-review |
| description | Guide on how to review GSV packages before approval, including source inspection, manifests, capabilities, entrypoints, staged edits, refs, and trust boundaries. |
Start from metadata, then verify with source:
pkg list
pkg show <package>
pkg manifest <package>
pkg capabilities <package>
pkg source <package>
rgit refs --here
rgit log --here --limit 20
rgit status --here
A review should usually start from clean source. If staged edits exist, explain what they are before trusting the tree.
Inspect the path reported by pkg source <package> directly. Identify browser, backend, CLI, public route, daemon, signal, and package profile entrypoints.
Use these only when the user asked for that action:
pkg add --repo owner/repo --ref main --subdir .
pkg approve <package>
pkg enable <package>
pkg disable <package>
pkg checkout <ref> <package>
pkg public on <package>
pkg public off <package>
Approval and enablement are separate. Approval trusts a package for its requested grants. Enablement activates entrypoints.
Lead with findings when risks exist. End with one clear verdict:
Do not approve based on display name, description, screenshots, or UI polish alone.