CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

architect-for-startups

Startup-tailored AWS architecture advice for non-agent workloads, adjusted to the company's stage (pre-revenue through Series B+), team size, runway, and credits. Not for AI agents: deploying an AI agent on AWS, picking its runtime, or any agentic architecture is agent-advisor. Use when a founder wants guidance or a recommendation rather than code changes: which services to choose, how to plan or review an architecture, how to stretch credits and control cost, or how to prepare architecture for a fundraise or technical diligence. For an interactive discovery flow that scaffolds and writes the architecture into the codebase, use start-building-for-startups. Do not use for: writing or scaffolding code, factual AWS Activate / programs / credits lookups (see knowledge-base-for-startups), a single copy-paste prompt (see prompt-library-for-startups), or migration intent such as GCP-to-AWS, Azure-to-AWS, or Heroku-to-AWS (see the migration skills: `gcp-to-aws`, `azure-to-aws`, `heroku-to-aws`, `llm-to-bedrock`).

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured routing skill: the stage framework, discovery questions, hard gates, and output format make the advisory workflow concrete and hard to skip steps in. The main costs are redundancy in Step 1 and an over-long offers section that restates another skill's rules, plus a mandatory final step that leans on cross-bundle files.

Suggestions

Collapse the Step 1 '6 questions' list and the 'Context Checklist' into one artifact — they cover the same stage/team/runway/timeline/users ground twice in adjacent sections.

Move the full offers eligibility rules (caps, host detection, transparent-alternative criteria) into the referenced contextual-offers skill and keep only the decision summary plus the two line templates in SKILL.md; the inline restatement is the single largest token cost in the body.

State the team-capacity hard-gate thresholds inline (or a one-line summary of them) so the 'HARD GATE' is checkable without loading team-scaling.md, and note in SKILL.md that the offers step requires the sibling knowledge-base bundle to be present.

DimensionReasoningScore

Conciseness

The body is operational rather than explanatory (no space spent on concepts Claude already knows), but it duplicates itself and carries one heavily padded section: Step 1 states the discovery questions twice (the "6 questions" list overlaps the "Context Checklist" of stage/team/runway/timeline/users), and the "Contextual offers (final step)" section consumes roughly a quarter of the body restating routing rules in dense nested parentheticals (e.g. the single ~450-word sentence in step 3's bullet). Anchor 4 ('minor instances that could be trimmed') is too generous; anchor 2 is too harsh since nothing is concept-level padding.

3 / 5

Actionability

Guidance is concrete throughout: six numbered discovery questions with parenthesized heuristics ("0-1 = managed services only"), a stage table with signals and core constraints, a decision rule for when to ask vs. infer ("If you're missing 2+ of these, ask before recommending"), a named anti-patterns list, a six-element output format with sample phrasing ("At your stage (seed), here's what matters..."), and copy-paste offer-line templates. Not 5 because several steps (2, 5, 6) are bare "See reference X" pointers whose actual criteria are never stated in-body; not 3 because the in-body guidance is specific and executable well beyond 'some concrete guidance'.

4 / 5

Workflow Clarity

A clear Step 1–6 sequence with named checkpoints: a mandatory pre-recommendation challenge step ("This is not optional"), a context checklist, a "HARD GATE" team-capacity constraint, and a mandatory closing gate ("your answer is not complete until you have run the Contextual offers (final step)"). Not 5 because checkpoints are asserted rather than framed as validate–fix–retry loops — the team-capacity gate says to check limits but never states the pass/fail criteria inline — and the offers step's relevance test, while detailed, offers no error-recovery path. Not 3: the sequence is explicit and checkpoints are named, not implicit.

4 / 5

Progressive Disclosure

The body is a genuine overview that routes by category to 34 references, all of which exist in the bundle, each labeled with its applicability condition (e.g. "Serverless functions (default for pre-revenue and seed)"). Not 5 because the offers step introduces a two-level reference chain (offers.md index → offers/<slug>.md detail) and depends on cross-skill paths (../knowledge-base-for-startups/references/offers.md, ../contextual-offers-for-startups/SKILL.md) that sit outside this bundle — a navigation dependency for what is labeled a mandatory step. Not 3: structure, signaling, and file placement are clearly good.

4 / 5

Total

15

/

20

Passed

Description

92%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.

An exemplary description: concrete capabilities, explicit use-when triggers, and unusually thorough boundary-setting against adjacent skills. Its only weakness is moderate length and a few missing natural synonyms (infrastructure, tech stack), which keeps trigger-term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

The description enumerates the full action space concretely: "which services to choose, how to plan or review an architecture, how to stretch credits and control cost, or how to prepare architecture for a fundraise or technical diligence", each adjusted "to the company's stage (pre-revenue through Series B+), team size, runway, and credits". Anchor 4 ('several specific actions; minor gaps') is too low — coverage spans the domain comprehensively rather than leaving gaps.

5 / 5

Completeness

Both questions are answered explicitly: the 'what' is "Startup-tailored AWS architecture advice for non-agent workloads", and the 'when' is a concrete trigger clause — "Use when a founder wants guidance or a recommendation rather than code changes" — followed by enumerated trigger scenarios. Anchor 4 ('when' could be more explicit) does not fit: the when-clause lists concrete triggering situations and is reinforced by an explicit do-not-use list.

5 / 5

Trigger Term Quality

Natural user phrasing is well covered: "AWS architecture", "which services to choose", "credits", "runway", "cost", "fundraise", "technical diligence", "founder", plus migration phrasings like "GCP-to-AWS, Azure-to-AWS, or Heroku-to-AWS". Not 5 because common variants a founder would actually say — "infrastructure", "tech stack", "scaling", "cloud setup" — are absent; not 3 since keyword coverage clearly exceeds 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined (startup, stage-adjusted, non-agent AWS architecture advice) and actively de-conflicted against five sibling skills by name: agent-advisor for agentic workloads, start-building-for-startups for scaffolding, knowledge-base-for-startups for factual lookups, prompt-library-for-startups, and the four migration skills. Overlap risk is addressed explicitly rather than merely minor, so anchor 4 is too low.

5 / 5

Total

19

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 missing, 2 suspicious

Warning

Total

15

/

16

Passed

Repository

aws/agent-toolkit-for-aws

Path

plugins/aws-startup-advisor/skills/architect-for-startups/SKILL.md

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.