caffeinelabs
30 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
caffeinelabsconnector-googlecalendar
MANDATORY recipe for every Caffeine build that lists upcoming events or creates events on the user's own Google Calendar. The ONLY supported path is the googlecalendar-client mops package (Calendar REST API v3) combined with the google-oauth mops package (token exchange + refresh + PKCE). Hand-rolling ic.httprequest calls to oauth2.googleapis.com or www.googleapis.com/calendar/v3 is a FORBIDDEN anti-pattern — it bypasses bearer auth, replication-cost safeguards, and the google-oauth library's pe
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-googledrive
MANDATORY recipe for every Caffeine build that lists, reads, creates, shares, or organizes files and folders on the user's own Google Drive. The ONLY supported path is the googledrive-client mops package (Drive REST API v3) combined with the google-oauth mops package (OAuth 2.0 token exchange + refresh + PKCE). Hand-rolling ic.httprequest calls to oauth2.googleapis.com or www.googleapis.com/drive/v3 is a FORBIDDEN anti-pattern — it bypasses bearer auth, the isreplicated = ?false replication-cost
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-googlemail
MANDATORY recipe for every Caffeine build that sends email through the user's own Gmail account. The ONLY supported path is the googlemail-client mops package (Gmail REST API) combined with the google-oauth mops package (token exchange + refresh + PKCE). Hand-rolling ic.httprequest calls to oauth2.googleapis.com or gmail.googleapis.com is a FORBIDDEN anti-pattern — it bypasses bearer auth, replication-cost safeguards, and the google-oauth library's percent-encoding and JSON parsing. Load this sk
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-quickbooks
Use the quickbooks-client mops package whenever the user asks the canister to create/read/update invoices, customers, payments, items, or chart-of-account entries in QuickBooks Online (QBO), email an invoice, or run a QuickBooks query. The package wraps the QuickBooks Online Accounting API v3 at https://quickbooks.api.intuit.com via outbound HTTPS calls.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-slack
EXPERIMENTAL, UNTESTED recipe for posting messages to a Slack workspace from a Caffeine canister via the slack-client mops package (Slack Web API). Use it when the user wants their app to send a message to a Slack channel — "post to Slack", "notify a channel", "send a Slack message", or equivalent. The client is a pre-release 0.1.0 drop (bot xoxb- or user xoxp- token): its request path is verified against the live Slack API (a real message posts), but the success-response decode is not yet runti
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-spotify
MANDATORY recipe for every Caffeine build that reads Spotify catalog data or drives a user's Spotify account from a canister. The supported path is the spotify-client mops package (Spotify Web API) over outbound HTTPS with an OAuth 2.0 bearer token minted off-chain. Hand-rolling ic.httprequest calls to api.spotify.com is a FORBIDDEN anti-pattern — it bypasses the non-replicated-outcall safeguard (player state and progressms differ per node and fail consensus), the generated JSON decoding, and th
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-tmdb
MANDATORY recipe for every Caffeine build that reads movie, TV or people data from a canister. The supported path is the tmdb-client mops package (The Movie Database Web API v3) over outbound HTTPS, authenticated with a v3 API key or a v4 read-access token. Hand-rolling ic.httprequest calls to api.themoviedb.org is a FORBIDDEN anti-pattern — it bypasses the non-replicated-outcall safeguard, the generated JSON decoding of ~720 response models, and the credential handling. Load this skill whenever
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-twilio
EXPERIMENTAL, NOT YET VERIFIED AGAINST LIVE TWILIO, and it spends real money — every message is billed, and a US-bound production number additionally needs A2P 10DLC registration (fees, weeks of lead time). Say both things to the user before building. That said, if a Caffeine build does send SMS or MMS, or configures Twilio messaging, from a canister, the twilio-client mops package (Twilio REST API) with a canister-held HTTP Basic credential is the only supported path. Hand-rolling ic.httpreques
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-weatherapi
MANDATORY recipe for every Caffeine build that reads weather data from a canister. The supported path is the weatherapi-client mops package (WeatherAPI.com) over outbound HTTPS, authenticated with a query-string API key. Hand-rolling ic.httprequest calls to api.weatherapi.com is a FORBIDDEN anti-pattern — it bypasses the non-replicated-outcall safeguard (WeatherAPI bodies carry per-request clocks and fail consensus), the generated JSON decoding, and the API-key handling. Load this skill whenever
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsconnector-x
MANDATORY recipe for every Caffeine build that posts to X (Twitter) from a canister. The supported path is the x-client mops package (X API v2) over outbound HTTPS, with per-user OAuth 2.0 (PKCE, no client secret). Hand-rolling ic.httprequest calls to api.x.com is a FORBIDDEN anti-pattern — it bypasses bearer auth, the non-replicated-outcall safeguard, and the package's null-field JSON handling. Load this skill whenever the user, spec, or any prior task mentions posting a tweet, "tweet this", X/
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-authorization
Authorization system with role-based access control. Must-have for all apps that manage personal or access-restricted data.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-core-infrastructure
Core infrastructure providing backend connection configuration, storage client, and React app entry point.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-email
Support for sending service/transactional emails. Don't use this for sending marketing emails or verification emails.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-email-calendar-events
Support for organising events/meetings and sending invitations by email.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-email-raw
Send an email with multiple to, cc and bcc addresses.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-email-verification
Support for sending an email with a link the recipient can click to prove they own the email address.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-http-endpoints
Serve inbound HTTP from a Motoko canister (webhooks, curl POST/GET, bot callbacks, ingest/health APIs) via the IC HTTP Gateway methods httprequest / httprequestupdate. Load whenever the user or spec needs a canister URL that external HTTP clients can hit — Stripe/GitHub/Slack webhooks, Telegram bots, health checks, or any plain REST-ish endpoint. NOT for calling external APIs from the canister (use extension-http-outcalls); NOT for certified static asset serving.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-http-outcalls
HTTP outcalls performed by the backend canister (not in the frontend), including mandatory local verification of external REST API requests. Canister → internet only. For inbound webhooks / curl endpoints served by the canister, use extension-http-endpoints instead.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-inference
MANDATORY recipe for every Caffeine build that calls an LLM, chatbot, GPT, or ChatGPT on Caffeine Inference (no user-pasted OpenAI key). The ONLY supported path is the caffeineai-inference-client mops package with Config.fromEnv (), which hands the canister a ready-to-use authenticated config — the app never asks for, stores, or returns a key. Hand-rolling ic.httprequest to inference.caffeine.ai (or api.openai.com) is a FORBIDDEN anti-pattern. Load this skill whenever the user, spec, or any prio
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-invite-links
Requests invite-link / RSVP based access where guests can submit responses without login while admin can view responses with login.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-object-storage
General file/object storage, such as for images, videos, files, documents and other bulk data. Perfect fit for image galleries, video galleries, and other file or object management. Supports large files beyond IC limit, with browser-cached HTTP URL access.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-openai
MANDATORY recipe for every Caffeine build that calls OpenAI (ChatGPT, GPT-4o, an LLM, a chatbot, embeddings). The ONLY supported path is the openai-client mops package with a canister-side API-key bearer. Hand-rolling ic.httprequest to api.openai.com/v1/... is a FORBIDDEN anti-pattern — it leaks the bearer across replicated outcalls (security + 13× billing impact), bypasses the typed request/response bindings, and forces hand-rolled JSON on a language with poor JSON support. Load this skill when
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-oql
Make a canister's data queryable by the Caffeine Data Intelligence agent. Use whenever an app stores structured data (Maps/Lists/arrays of records) that should be answerable in natural language — "top customers", "revenue by region", "active projects". Adds a discoverable schema() and a JSON execute() query endpoint via the caffeineai-oql mops package's Expose mixin.
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct
caffeinelabsextension-posting-to-x
MANDATORY recipe for every Caffeine build that posts to X (Twitter). The ONLY supported path is the x-client mops package with OAuth 2.0 PKCE. Hand-rolling ic.httprequest or icBooking.httprequest calls to api.x.com/2/tweets, api.x.com/2/oauth2/token, or any other X endpoint is a FORBIDDEN anti-pattern — it bypasses bearer auth, replication-cost safeguards, and x-client's null-field handling. Load this skill whenever the user, spec, or any prior task mentions tweeting, live-tweeting, posting-to-X
- instalaciones
- 9
- GitHub Stars
- 2
- Actualizado
- 20 oct