extension-authorization
Build Role-Based Authorization for Caffeine AI
Applications need consistent authentication and role checks across Motoko backends and React frontends. This skill provides Caffeine AI patterns for protected endpoints, profiles, login state, and migrations.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "extension-authorization" from https://skillstore.io/skills/caffeinelabs-extension-authorization.md and its manifest at https://skillstore.io/api/skills/caffeinelabs-extension-authorization/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "extension-authorization". Add authorization to an application where users edit their own records and administrators manage every record.
Expected outcome:
- A role model covering administrators, users, and guests.
- Backend guard placement for every protected read and write operation.
- Ownership checks that permit users to edit only their own records.
- Frontend behavior for login, access denial, and logout cleanup.
Using "extension-authorization". Upgrade an existing application and store the verified email after sign-in.
Expected outcome:
- A dependency upgrade checklist for backend and frontend packages.
- A callback design that stores only verified identity attributes.
- A caller-scoped method for retrieving the saved email.
- Verification steps for compilation, sign-in, and restored sessions.
Security Audit
High RiskAll 67 static findings are false positives caused by Markdown, code examples, relative links, imports, or descriptive identity text. No external command execution, path traversal, reconnaissance, or runtime network request is present. A separate high-severity bootstrap risk allows the first authenticated user to become administrator without prior authorization.
Confirmed security concerns (1)
Risk Factors
๐ Filesystem access (3)
โ๏ธ External commands (50)
๐ Network access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/caffeinelabs-extension-authorization/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/caffeinelabs-extension-authorization?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/caffeinelabs-extension-authorization?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/caffeinelabs-extension-authorization/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/caffeinelabs-extension-authorization.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
caffeinelabs. (2026). extension-authorization security audit report (audit version 3) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/caffeinelabs-extension-authorization/audits/3BibTeX citation
@techreport{caffeinelabs-caffeinelabs-extension-authorization-2026,
author = {caffeinelabs},
title = {extension-authorization security audit report (audit version 3)},
institution = {Skillstore},
year = {2026},
number = {3},
url = {https://skillstore.io/skills/caffeinelabs-extension-authorization/audits/3},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "extension-authorization security audit report (audit version 3)"
version: "1.0.0"
type: report
authors:
- name: "caffeinelabs"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/caffeinelabs-extension-authorization/audits/3"
identifiers:
- type: other
value: "skillstore:caffeinelabs-extension-authorization:audit:3"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Protect a New Caffeine AI Application
Add standard roles, guarded Motoko endpoints, profiles, and Internet Identity login to a new application.
Build Reliable Authentication Screens
Coordinate restored sessions, login progress, profile setup, logout, and cached data in a React interface.
Upgrade Authorization Dependencies
Migrate authorization and core infrastructure packages while adopting the verified attribute callback.
Try These Prompts
Add Caffeine AI authorization to my application. Create administrator, user, and guest access with guarded backend endpoints.
Implement user profiles with owner and administrator access. Include profile setup after login and clear cached profile data during logout.
Migrate my existing authorization integration from version 0.x to 1.x. Update dependencies and add the optional verified attribute callback.
Review my Motoko and React authorization flow. Identify missing role checks, ownership checks, session-state errors, cache leaks, and administrator bootstrap risks.
Best Practices
- Apply backend authorization checks to every protected operation.
- Verify resource ownership in addition to checking broad user roles.
- Clear all user-specific cached data when the identity logs out.
Avoid
- Do not rely on hidden frontend controls as an authorization boundary.
- Do not gate restored sessions on interactive login success state.
- Do not expose personal records through unguarded query methods.
Frequently Asked Questions
Which applications fit this skill?
Does it support role-based access control?
Can it capture a verified email?
Does frontend access control protect backend data?
Can it migrate an older integration?
How is the first administrator selected?
Developer Details
Author
caffeinelabsLicense
MIT
Author version
v1.0.0
Skillstore revision
r2
Ref
a39a91716eadede5f4cdefd78178fed4e837a128
Maintenance freshness
7/24/2026
Usage
0 downloads ยท 0 views
File structure