agentsclimarketplace

Deployment

Skill verticalbarHQ/verticalbar-agent/skills/deployment

Assemble a CrossCheck Release Package and run it through a CI workflow — create the package, add customization items, then start a workflow run and follow it. Use when the user wants to deploy, promote, or release NetSuite customizations between environments, asks what a release contains, wants a CI workflow started or its run status, or says deploy / release / promote / 배포 / 릴리스. These are the only mutating tools this plugin exposes; read the authorization rules below before calling one.From its SKILL.md

Install
npx -y skills add verticalbarHQ/verticalbar-agent --skill deployment

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 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.

SKILL.md

5.0 KB, as published. Nobody here has run it

Deployment — release packages and CI workflow runs

Four read tools and three that mutate. The mutating three are the only writes this plugin performs against CrossCheck, and they are governed differently from everything else here.

ToolKindRequires
cc_list_release_packages, cc_get_release_packagereadworkspace scope
cc_list_ci_workflows, cc_get_ci_workflow, cc_get_ci_workflow_runreadworkspace scope; API-key mode fine
cc_create_release_packageMUTATESdeploy:write
cc_add_release_package_itemsMUTATESdeploy:write, package still a draft
cc_start_ci_workflow_runMUTATESan identified Cognito user — an API key cannot start a run

The authorization rule that trips people

cc_start_ci_workflow_run needs a real signed-in human. No API key can start a run, however broad its scope — this is a server guard, not a client check, so you cannot work around it and should not try. If CC_API_KEY is all that is set, creating and filling a package works and starting the run does not.

When a run is refused for identity, the fix is to sign in: use the setup skill, then retry. Do not report the refusal as a workflow problem.

cc_start_ci_workflow_run requires fresh human interaction in the MCP host before every call. This confirms creation of deployment intent; it does not approve a Pipeline stage. Stage approval still happens in CrossCheck, by a person. Never imply the plugin can approve that stage.

The order, and why it is the order

  1. Resolve workspace routing from runtime_info. With Cognito, call cc_workspaces: use the sole result automatically. If more than one is returned, ask the user to choose by safe name. Never select the first, invent an id, or reuse one after the conversation changes workspace. With api-key-bound routing, do not call cc_workspaces and omit workspaceId from every call; the server derives the authoritative workspace from the key.
  2. cc_create_release_package {workspaceId?, name, description?, environmentId?} — returns the server response unchanged, including the package id you will need next.
  3. cc_add_release_package_items {workspaceId?, packageId, items[]} — the response carries autoInclude.status. Read it. CrossCheck may pull in dependencies you did not list, and that set is what will actually deploy. Report what autoInclude added, not what you asked for. Items can only be added while the package is a draft; a package past that state refuses, and the refusal is the server's, so surface it verbatim rather than retrying.
  4. cc_list_ci_workflows / cc_get_ci_workflow — pick the workflow and read its ordered stages. cc_get_ci_workflow joins each stage to its environment name, which is the only readable way to confirm a promotion is aimed where the user thinks it is. Confirm the target environment with the user before step 5 whenever the workflow touches production.
  5. cc_start_ci_workflow_run {workspaceId?, workflowId, packageId} — the request body is exactly the package id. The host must ask a person immediately before this call. Returns the server response unchanged; actual environment writes remain blocked on CrossCheck stage approval.
  6. cc_get_ci_workflow_run — poll for status. A started run is not a finished one; do not report a deployment as done from the start call's response.

Reporting

  • The server is authoritative on everything — authorization, identity, workspace, draft state, baseline rules. These tools return its response unchanged by design. Quote it; do not paraphrase a refusal into your own words, and never soften one into "it may not have permission".
  • Say what is in the package, from cc_get_release_package after the adds, not from the list you submitted — autoInclude is exactly the gap between the two.
  • A run has stages. "Started" is one fact and "passed" is another; give the run id and the stage it is on rather than a single verdict.

Do not

  • Do not create a package to "see what happens". These are writes to a customer's release pipeline.
  • Do not start a run the user did not ask for, and never as a way of testing that a package is valid.
  • Do not retry a refused mutation with different arguments hoping it lands — a refusal names its reason, and working around it is the one thing this governed exception exists to prevent.

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.