More screenshots
Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsAutomation client request tracker
Evidence-based tracker that identifies missing, unverified, risky, and genuinely blocking automation access.
$9.99
Automation client request tracker
Example session with this skill installed
Client sent a PDF saying "AWS access granted" and a redacted IAM ARN, but the dev team says the AWS S3 command returns 403. The S3 bucket is required for the production automation and there is no workaround. The client says access was already provided.
Also, an old project note says an API token was created months ago, but nobody has confirmed whether it is still valid or even required.
Project launch is in 2 days.
Analyze the access situation and tell me what is actually blocking the project, what only needs verification, and what I should do next. Do not request or reproduce any secrets.
- Read your context and instructions
- Compiled the automation client request
Access Risk Assessment
The evidence shows one proven production access blocker and one separate unknown/evidence-gap item.
1. Access Risk Board
| Requirement | Access State | Verification | Blocker Impact | Priority |
|---|---|---|---|---|
| AWS S3 Production Bucket | RECEIVED — UNVERIFIED | NOT VERIFIED | YES — PROVEN BLOCKING | P1 |
| Historical API Token | UNKNOWN | NOT ESTABLISHABLE | UNKNOWN — INSUFFICIENT EVIDENCE | P2 |
2. Evidence Chains
AWS S3 Production Access
Evidence: Client claims access was granted; developer reports the S3 command currently returns 403; S3 is required for the production automation; no workaround exists.
→ Access State: RECEIVED — UNVERIFIED
→ Verification State: NOT VERIFIED
→ Blocker Impact: YES — PROVEN BLOCKING
→ Priority: P1
Why: There is direct operational evidence that the required production dependency cannot currently be accessed, and no viable workaround is available.
The redacted IAM ARN is metadata only. It does not prove that the correct permission was granted or that the access is usable.
Historical API Token
Evidence: An old project note mentions a token, but its current validity, system, authorization, ownership, and requirement are unknown.
→ Access State: UNKNOWN
→ Verification State: NOT ESTABLISHABLE
→ Blocker Impact: UNKNOWN — INSUFFICIENT EVIDENCE
→ Priority: P2
Do not treat the historical token as current access and do not request or reproduce the token.
3. Immediate Actions
- Escalate the AWS S3 access issue as the current proven blocker.
- Ask the client/admin to confirm the intended AWS identity and required S3 permission through the approved secure access process.
- Re-test the approved connection after the permission issue is corrected.
- Do not assume administrator access is required merely because the current access returns 403.
- Separately clarify whether the historical API token is still required and which system it belongs to.
4. Launch Risk
The client-stated launch target is 2 days away. This increases urgency but is not treated as a formal SLA or access deadline because no such agreement was provided.
Current Status
BLOCKED BY CLIENT ACCESS — AWS S3 production dependency
The API-token issue remains an evidence gap, not a proven blocker.
Security Check: PASS — no secret was requested, stored, or reproduced.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
Automation Client Access Request Tracker
Stop losing automation projects to unclear, missing, or unverified client access.
This skill turns messy client access information into a structured, evidence-based access tracker for automation freelancers, consultants, and agencies.
It helps you determine:
- What access is actually required
- What the client claims they provided
- What has actually been received
- What has been verified
- What is genuinely blocking delivery
- What is only a potential risk or evidence gap
- Which access items need follow-up
- Which permissions may be excessive
- Which production access is approaching expiry
- Which client or project needs attention first
Why it is different
The tracker does not treat every missing credential as a blocker.
It follows a strict evidence chain:
Evidence → Access State → Verification State → Blocker Impact → Priority
This means client confirmation is not automatically treated as usable access, received access is not automatically treated as verified, and an unverified item is not automatically labeled a blocker.
The skill also handles contradictory records and stale information by preserving the evidence and weighing current operational evidence appropriately.
Security-first
The skill never asks you to paste or store passwords, API keys, access tokens, private keys, recovery codes, or session cookies.
It tracks access metadata and verification status instead of secrets.
It also applies least-privilege thinking and separates authentication from authorization.
Scope protection
Client feature requests, routing changes, and business-rule changes are kept separate from access tracking so that a request to "just add one thing" does not silently become an access requirement or get absorbed into the onboarding process.
Built for real automation operations
Use it with client messages, access lists, developer notes, workflow documentation, project records, launch information, verification evidence, and portfolio-level access data.
It can operate at both project and multi-client portfolio level.
The goal is simple:
Know what access is ready, what isn't, what's genuinely blocking delivery, what needs verification, what is becoming risky, and which client needs attention first — without handling their secrets.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 7 days ago
- Passed all security checks, Safe to install