From cloudbees-unify
Onboard a GitHub repository to CloudBees Unify by creating one or more components and triggering a security scan. Use when the user says things like "onboard this repo to Unify", "add this project to CloudBees Unify", "register this repo in Unify", "create a Unify component for this repo", "set up this repo in CloudBees", or "connect my repo and run a security scan".
How this skill is triggered — by the user, by Claude, or both
Slash command
/cloudbees-unify:onboard-repo-to-unifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Before starting, confirm the user has:
Before starting, confirm the user has:
If either is missing, stop and advise them to get the necessary permissions first.
Verify Unify connection — call user_whoami. If it errors, tell the user to
check /mcp and run /reload-plugins.
Get org ID — call organizations_list_suborganizations. Auto-select if only
one exists; otherwise ask the user to pick.
Find SCM endpoint — call endpoint_list (contributionTypes: "cb.platform.endpoint-type").
Get repo details — run git remote get-url origin for the URL and
git symbolic-ref refs/remotes/origin/HEAD | sed 's|.*/||' for the default
branch (fall back to main).
Check for existing components — call components_list. If this repo URL is
already registered, show the existing component and confirm before proceeding.
Create component(s) — call components_create with name, endpoint_id,
organization_id, repository_url, default_branch. The component name
defaults to the last segment of the repo name. Do not offer to create duplicate components for the same repo URL.
Creating a component automatically triggers a security scan in the background.
Guide the user to view scan results — after the component is created:
Summarize and suggest next steps — confirm what was created (name, repo URL, branch, org), then offer:
npx claudepluginhub cloudbees-oss/cloudbees-unify-ai-plugin --plugin cloudbees-unifyGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.