setup-cloak
Skill8 starsChanged 9 months agoApache-2.0View on GitHub
Set up CLOAK development environment. Use when the user wants to install, configure, or troubleshoot CLOAK setup.
- Reads credentials
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run verification to check current status:
- Very specific: line 20
Note: Always use poetry run python to ensure the script runs in the Poetry virtual environment with all dependencies available.
- Distinctive: line 32
Verify Python 3.11+ is installed.
- Distinctive: line 58
Run the verification script again to confirm all components are ready.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLOAK Setup
Guide users through CLOAK environment setup.
Verification
Run verification to check current status:
poetry run python .claude/skills/setup-cloak/scripts/verify_setup.pyThe script outputs JSON with status of each component. Use this to determine which steps are needed.
Note: Always use poetry run python to ensure the script runs in the Poetry virtual environment with all dependencies available.
Requirements
- Python 3.11+
- Poetry (package manager)
- AWS credentials with read permissions
Setup Workflow
Step 1: Python
Verify Python 3.11+ is installed. If not, user must install Python first.
Step 2: Poetry
Install Poetry if not available. Use pipx (recommended) or the official installer.
Step 3: Dependencies
poetry installStep 4: AWS Credentials
Configure AWS credentials using any standard method (environment variables, ~/.aws/credentials, SSO, or IAM role).
Required permissions: See docs/SETUP.md for the complete IAM policy.
Step 5: Validate
poetry run python -m cloak.cli --validate-connectionStep 6: Final Verification
Run the verification script again to confirm all components are ready.
Success Criteria
Setup is complete when verify_setup.py shows "ready": true.
Troubleshooting
See docs/TROUBLESHOOTING.md for common issues.
Next Steps
Setup is complete! Here are some things you can try:
S3 Storage Security
- "Enumerate all S3 buckets in my account and check for public access"
- "Review bucket policies for overly permissive configurations"
IAM Identity Assessment
- "List all IAM users and show me which ones have console access"
- "Check IAM roles for excessive permissions"
EC2 Network Security
- "Find security groups with unrestricted inbound access (0.0.0.0/0)"
- "Review my VPC configurations"
Lambda Function Security
- "Enumerate Lambda functions and their resource-based policies"
Or invoke a skill directly for guided assessments: /aws-s3, /aws-iam, /aws-ec2, /aws-lambda
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

