Guide a developer through connecting a repository to AWS Continuum, granting least-privilege access, creating an environment, learning the real deployment, and observing its automatic first scan.
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/aws-continuum/skills/setting-up-continuum/SKILL.mdUse the native AWS CLI for every Continuum operation. Use only the public API with the credential selection governed by the shared AWS safety prelude. Never use internal endpoints, machine-only operator credentials, or service databases.
AWS_IGNORE_CONFIGURED_ENDPOINT_URLS=true on every aws invocation. Run CLI version/help and local Git discovery; these are not AWS service reads.--expected-bucket-owner <caller-account>. A server-side copy must also include --expected-source-bucket-owner. list-buckets and create-bucket do not accept the guard; after creation, perform guarded head-bucket before any other call. A mismatch or ambiguous 403 fails closed.--profile when selected, the explicit resolved --region, --output json, and --no-cli-pager. No explicit endpoint override is accepted for any service. Neutralize inherited and profile-configured endpoints as the shared prelude requires.patchCreationPolicy. If patch creation is disabled, say once in the plan: Continuum won't create patches, so it won't open pull requests. If the source is S3, ask no delivery question; say once that Continuum patch previews land in the bucket under continuum-patches/ as references only. Only for a GitHub source with patch creation enabled, say once that Continuum may open its own pull requests alongside the plugin's, suggest turning off its pull-request delivery or patch creation, and ask at most one simple optional question. Accept any answer, never repeat it, and never block setup. Do not name a console route or control unless current public AWS Continuum documentation confirms it; never direct the developer to a console create form because this workflow creates the environment through the API.State the current step's end condition before starting it, then keep working until that condition is reached. Do not end a turn with “I’m continuing,” a progress-only update, or a request for a generic “Continue.” Return control only for these explicit gates: profile and region choice, confirmation of the STS account, confirmation of material deployment facts, approval of an exact write set, the post-setup choice of how to follow the already-started first scan, or a fatal safety precondition that needs the developer to choose a remedy.
For waits, use a bounded condition loop around a read-only check, for example:
timeout 580 bash -c 'until <read-only-completion-check>; do sleep 30; done'If the command reaches its bound while the stated end condition is still pending, re-run the same bounded loop and continue in the same task. Never chain fixed sleeps such as sleep 15; ...; sleep 30, and never create another scan merely because a wait window ended.
List and hydrate all pages from the public API:
aws continuum list-environments --max-results 100 --no-paginate ...
aws continuum get-environment --environment-id <id> ...
aws continuum list-integrations --max-results 100 --no-paginate ...
aws continuum get-integration --integration-id <id> ...For these service-token commands, --max-results and --next-token may be used with --no-paginate; manually follow nextToken and stop on repeated tokens. Do not combine --no-paginate with the AWS CLI paginator flags --page-size, --max-items, or --starting-token—the CLI rejects that combination. For list-code-scans, prefer normal CLI auto-pagination with optional --page-size 100, and omit --no-paginate, --max-items, and --starting-token. Prefer a fitting existing integration and environment. A name match alone is insufficient: verify source repository or S3 prefix, role, bucket, recurrence, patch policy, region, and account. Reuse means zero configuration writes; never silently repoint or update an existing environment.
For an S3 source, guard every bucket request. Inspect the role, every inline and attached policy version, permission boundary, bucket policy, KMS key policy where relevant, and trust. If evaluation is uncertain, say so. Never edit an existing trust or permission statement. A permission gap may be added only as a new uniquely named inline policy after a separate approved plan. A trust gap means choosing another role or creating a new role.
Read setup-details.md before preparing any IAM, bucket, integration, upload, or environment write. Before upload, complete safety-contract item 10. Do not prepare an upload or environment write set unless the repository count passes the documented quota preflight. Put the per-integration count, total, effective limit, quotas-page citation, ZIP-size measurement and remaining ZIP-size risk in the exact plan. Publish the complete first source version before environment creation, using the reporting skill's packaging contract. The setup plan must say: Write a small upload record so an interrupted upload is never mistaken for a complete one. Use one record at <codePrefix>.continuum/uploads/v<N>.json: conditionally create status uploading, verify every zip, then conditionally update that same record to status complete with its ETag.
Before suggesting fixes, inspect non-secret source configuration, process definitions, containers, infrastructure, developer docs, ports, proxy or tunnel hops, TLS termination, sign-in methods, trusted headers, development mode, machine clients, restarts, and recovery. This produces a source-derived draft, not deployment truth.
Discuss each material fact with the developer and confirm:
Read deployment-profile.md for the shape. With consent, save private facts to .continuum/deployment-profile.local.md and add that exact path to the target repository's .git/info/exclude. Verify git check-ignore --no-index .continuum/deployment-profile.local.md. Never stage it. If the repository has no Git metadata, save outside the repository instead. Record provenance, confirmation time, unknowns, and no secrets.
Non-secret product decisions belong in the tracked .continuum/house-rules.md. Propose the file and protection mechanism (for example CODEOWNERS or branch rules) separately; do not create or alter either without approval.
Present the full plan in dependency order only after the repository quota preflight passes. If it fails, stop before any write and present its three remediation options instead.
Ask the developer to choose the scan cadence; do not infer it. Offer P1D, P2D, P7D, and no recurring scans (PT0H), while explaining that environment creation still starts the first scan automatically.
Apply safety-contract item 9 once when presenting the plan. For a GitHub source with patch creation enabled, the optional question can be included with the normal plan decisions; its answer is never a separate approval and never a prerequisite. Do not raise the topic for any other source-and-policy combination beyond the required single explanatory sentence.
Apply only the approved writes. Re-read every created resource and verify ownership and configuration. Then follow the local plan contract, editing the plan file yourself to append a setupCompletions record {environmentId, result, repositoryCount, repositoryQuota, quotaSource, quotaIncreaseStatement, recordedAt}, where result is configured or reused and quotaIncreaseStatement is present only when the developer said AWS granted a higher limit. Read back the record; never store secrets or overwrite prior history. This record has no patch-delivery prerequisite.
Creating an environment starts its first build and scan automatically. Do not call create-code-scan afterward. Capture the initial scan from environment or scan inventory and verify that exact scan has started. Setup ends at that point; do not hold setup open for scanner termination or the later validation/issue workflow. Explain that a first scan usually takes roughly 20–60 minutes and that a large repository or service queue can take longer. Do not promise a deadline.
Offer these explicit follow-up choices:
I'll report here; say exactly: A background agent is watching the scan. When you see it marked completed, ask me 'did the scan finish?' and I'll give you the result. Claude Code Task subagents have different foreground and background delivery behavior, so verify the active mode before describing it. For any host without a guaranteed parent wake, use the same completion-marker instruction. The subagent repeatedly performs a bounded read-only condition wait on this exact scan. It must not start a local process, timer, tmux session, watcher, or notification service./status or ask “where do we stand?” at any time. This performs a fresh bounded public read.For either kind of active wait, state that the end condition is either scan FAILED or the later validation and issue workflow settling after scanner SUCCEEDED. Re-run bounded condition loops until one end condition occurs. The monitor's final message must be short and self-contained: succeeded or failed, why, and the next step. On failure, include the public failureStage and failureMessage, explain their meaning in plain words, label likely causes as possibilities rather than facts, and recommend one concrete next check or re-plan. For WAITING_FOR_SCAN with a message that the source configuration is unsupported, retrieve the actual repository count and effective quota from the recorded setup preflight; if unavailable, recompute the count with read-only integration and guarded S3 inventory. When the count exceeds the quota, explain the likely cause in this form: This environment contains <COUNT> code repositories, but your account's current quota in <REGION> is <LIMIT> repositories per environment. The scan did not start. Then offer choosing <LIMIT> or fewer repositories, splitting the sources into logically grouped environments with <LIMIT> or fewer each, or asking the AWS account team for a quota increase. Do not blame ZIP size, Region, or source layout when their checks passed. If the count is within the effective quota, say the repository quota check passed and continue investigating other possible causes without presenting one as proven. On success, say exactly Scan finished: N validated issues, do not dump findings, and offer the whole-picture report.
If this setup started a monitor, then at the beginning of each later user turn inspect the host's monitor state before handling the new request. When the monitor has completed, read its result first and lead the response with that result. A completion marker alone is not the result and must not be presented as one.
Do not repeat patch-delivery advice or ask for another answer in the setup summary. If the developer chose to change the proposed GitHub patch policy, reflect that approved API value in the exact write set; otherwise continue with the approved plan.
Finish when the automatic first scan is observed as started. Return immediately with created or reused identifiers, every actual write, the initial scan ID and lifecycle, the typical 20–60 minute expectation, pending validation or issue work, local files, unknowns, the three supported follow-up choices above, and the next read-only /status or “where do we stand?” check. Do not create notifications or a local watcher.
aws/agent-toolkit-for-aws
292edb1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.