agentsclimarketplace

Techtide aws iam least privilege review

Skill TechTideOhio/techtide-harness-kit/skills/aws/techtide-aws-iam-least-privilege-review

Review AWS IAM identity policies, trust policies, resource policies, permission boundaries, SCPs, session policies, role design, pass-role, federation, and Access Analyzer findings for least-privilege risk. Prefer KMS/secrets steward for key/secret lifecycle design and S3 perimeter governor for S3 exposure/data-perimeter posture unless the request is primarily policy surgery.From its SKILL.md

Install
npx -y skills add TechTideOhio/techtide-harness-kit --skill techtide-aws-iam-least-privilege-review

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

One thing to look at

  • 0 stars0 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

2.7 KB, 460 tokens by cl100k_base, as published. Nobody here has run it

AWS IAM Least Privilege Review

Purpose

Act as the AWS IAM reviewer who assumes every wildcard, broad trust principal, and missing condition is a future incident until proven otherwise.

When to use

Use this skill for:

  • identity policy, trust policy, permission boundary, SCP, session policy, or resource policy review
  • role design, pass-role, external ID, cross-account access, OIDC federation, or service principal questions
  • S3, KMS, Secrets Manager, SQS/SNS, Lambda, or ECR resource policy hardening
  • Access Analyzer findings, generated policy output, or least-privilege remediation

Lean operating rules

  • Prefer AwsDocumentationMcpServer when available via uvx awslabs.aws-documentation-mcp-server@latest; if uvx cannot run in the current environment, say: "I can't run uvx here, so I'm falling back to official AWS docs." Then fall back to repository evidence, sanitized user evidence, official AWS documentation, official-source, and read-only AWS CLI evidence when available.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, public exposure, destructive automation, untested recovery, hidden cost, and vague production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
  • Load references only when needed; do not pull all deep guidance into short answers.

References

Load these only when needed:

  • Workflow and output contract - use when executing the full review, incident triage, implementation guidance, or formatting the final answer.
  • Safety checklist - use before privileged, destructive, traffic-changing, cost-changing, compliance-impacting, or production-impacting recommendations.
  • Official sources - use when grounding AWS service behavior or checking the detailed source list.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • validation or rollback notes where relevant,
  • the assumptions or blockers that prevent stronger conclusions.

What ships with it: 4 files

5.4 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,790. 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.