CtrlK
BlogDocsLog inGet started
Tessl Logo

aws-tenant-standup

Stand up or rebuild an AWS Shifter tenant end to end (teardown, bootstrap, secrets, image bakes, deploy via the real deploy.yml dispatch, health check, base-range smoke, and a POLARIS range walkthrough). AWS only. Use when asked to rebuild, redeploy, or stand up an AWS tenant such as proof or aws-dev from a clean state.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is aws-tenant-standup in PaloAltoNetworks/shifter

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced operational runbook with concrete commands, validation checkpoints, and explicit feedback loops. Structure is strong; only minor tightening and the absence of a local bundle layer keep it from full marks.

DimensionReasoningScore

Conciseness

Dense and operator-focused with minimal padding; each section earns its place, though a few narrative sentences around ground rules and known pitfalls could be tightened further.

4 / 5

Actionability

Provides copy-paste-ready commands throughout — `aws ... sts get-caller-identity`, `gh workflow run deploy.yml ...`, `scripts/portal-deploy/deploy_portal.sh --migrate-only` — with specific env/profile substitutions and exact file paths.

5 / 5

Workflow Clarity

Eight numbered phases are explicitly sequenced with validation checkpoints (preflight, health verification, smoke before POLARIS, poll to READY/FAILED) and explicit error-recovery loops (manual migrate over SSM, known-pitfall fixes).

5 / 5

Progressive Disclosure

Well-organized phase sections with clearly signaled references to authoritative docs and scripts one level deep; no bundle files exist, and the body is appropriately structured, but the overview-to-detail split relies on repo paths rather than local bundle files.

4 / 5

Total

18

/

20

Passed

Description

76%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete phases, concrete trigger terms, and a clear AWS-only niche. Minor room to expand trigger synonyms and the per-phase action granularity.

DimensionReasoningScore

Specificity

Lists multiple concrete phases — 'teardown, bootstrap, secrets, image bakes, deploy via the real deploy.yml dispatch, health check, base-range smoke, and a POLARIS range walkthrough' — but stays at the phase level rather than enumerating the granular actions within each.

4 / 5

Completeness

Answers both what (the full end-to-end process) and when ('Use when asked to rebuild, redeploy, or stand up an AWS tenant'); the 'when' is explicit but could name more trigger variations.

4 / 5

Trigger Term Quality

Includes natural operator phrases ('rebuild, redeploy, or stand up an AWS tenant') and concrete tenant names ('proof or aws-dev'); slightly short of comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The 'AWS only' scope plus named tenants ('proof', 'aws-dev') and the POLARIS-specific walkthrough carve a clear niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 6 missing, 4 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository
PaloAltoNetworks/shifter
Reviewed

Table of Contents

Is this your skill?

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.