[Akshat0694]

Two user-facing changes.

1. Next-steps prompts start from the user's own code

Before	After
Summarize my StackGuardian security posture and top misconfigurations	Deploy the Terraform in this repo and show me the plan before apply
Why did my latest workflow run fail? Show me the logs	Create an OpenTofu workflow for this repo that waits for my approval
Create a workflow from a marketplace template for an S3 bucket	Run our Ansible playbook as a StackGuardian workflow
Upgrade my workflows that use an outdated template version	Why did my latest deployment fail? Show me the logs

Each prompt works with what the wizard installs:

• Terraform and OpenTofu: sg-create-workflow with a git source (the OpenTofu prompt also sets an approval gate).
• Ansible: a custom step pipeline from a step template in the organization's library.
• The failed deployment: the MCP run and log tools.

Every prompt fits in an 80-column terminal.

2. A clickable link when a connector is missing

Before: an organization with no cloud or git connector got an improvised message. With two organizations connected, the agent even recommended continuing in the other one.

After: sg-create-workflow, sg-create-stack and sg-update-workflow have a "No connector yet" section. When a connector search finds nothing suitable, the agent:

• gives a markdown link to https://<dashboard>/orchestrator/orgs/<org>/settings/cloud-providers or …/vcs-providers;
• waits until the user has added the connector, then searches again;
• never switches to another StackGuardian organization or MCP server unless the user asks for that organization.

Where the link parts come from:

• <org>: source.filters.orgId, which every search response includes, even an empty one. I checked this against the live server.
• <dashboard>: app.stackguardian.io (Europe) or us.stackguardian.io (US), matched to the MCP server URL's region. If the agent can't tell the region, it gives both links.

The existing workflow-groups link used the same hard-coded Europe host, so it now follows the region too.

Follow-ups outside this repo

• These skills are copied by hand from sg-clickhouse-mcp (chore: sync skills from sg-clickhouse-mcp #24). The same edit is needed there, or the next sync removes it.
• Better long-term fix: have the MCP server return devPortalCloudConnectorsUrl / devPortalVcsConnectorsUrl, the same way it already returns devPortalWorkflowGroupsUrl. Return them both with empty connector results and with the availableConnectors / availableVcsConnectors errors. The server knows the region; the agent can only infer it.

CHANGELOG.md: both changes are added to the unreleased 1.3.0 entry.

Checks

• bun run typecheck: clean. bun run test: 23/23. CHANGELOG.md and commands.ts pass Prettier.
• I didn't run bun run fmt on the skill files: they aren't Prettier-formatted upstream, and it would rewrite them wholesale.
• Not tested: how the agent behaves with an organization that has no connectors. The organization connected on the test machine has both kinds.

🤖 Generated with Claude Code