RADAR DE SKILLS · GITHUB
Agent Skills útiles, ordenados por uso real.
Compara Skills verificados por función, contenido del paquete, instalaciones y fiabilidad de la fuente antes de añadirlos.
- ALCANCE DEL CATÁLOGO
- VERIFICADO
- Skills
- 5771
- repositorios
- 824
- última sincronización
- 8 sept 2026
its-a-skill-issuecharacter-design-sheet
Character consistency across AI-generated images with reference sheets and LoRA techniques. Covers turnaround views, expression sheets, color palettes, and style consistency tricks. Use for: character design, game art, illustration, animation, comics, visual novels. Triggers: character design, character sheet, character consistency, character reference, turnaround sheet, expression sheet, character art, consistent character, character concept, reference sheet, character creation, oc design, character bible
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 6 sept
its-a-skill-issueimage-to-video
Still-to-video conversion guide: model selection, motion prompting, and camera movement. Covers Wan 2.5 i2v, Seedance, Fabric, Grok Video with when to use each. Use for: animating images, creating video from stills, adding motion, product animations. Triggers: image to video, i2v, animate image, still to video, add motion to image, image animation, photo to video, animate still, wan i2v, image2video, bring image to life, animate photo, motion from image
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 6 sept
its-a-skill-issuestoryboard-creation
Film and video storyboarding with shot vocabulary, continuity rules, and panel layout. Covers shot types, camera angles, movement, 180-degree rule, and annotation format. Use for: video planning, film pre-production, ad storyboards, music video planning, animation. Triggers: storyboard, storyboarding, shot list, film planning, video planning, pre production, shot composition, camera angles, scene planning, visual script, animatic, storyboard panels, video storyboard
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 6 sept
jlui17mdnote
Review and apply annotations left on a Markdown file with mdnote (highlight-and-comment review for .md files). Trigger when the user says "I left notes", "check my annotations", "review my notes on ", asks you to look at feedback on a doc, or after you've pointed the user at a Markdown file for review.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 6 sept
hashicorpterraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
- instalaciones
- 2
- GitHub Stars
- 864
- Actualizado
- 4 sept
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 percent-encoding and JSON parsing. Load this skill whenever the user, spec, or any prior task mentions scheduling, calendar events, appointments, meetings, "add to calendar", or any equivalent phrasing — and BEFORE writing any code that touches a Google endpoint.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
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 skill whenever the user, spec, or any prior task mentions sending email, Gmail, "notify via email", "forward results by email", or any equivalent phrasing — and BEFORE writing any code that touches a Google endpoint.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
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 runtime-confirmed, so treat it as a starting point and do NOT present Slack as a fully supported platform feature yet. Hand-rolling ic.httprequest calls to slack.com/api is still the wrong move — prefer the generated client so bearer auth, percent-encoding, and JSON parsing come for free.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
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.httprequest calls to api.twilio.com or messaging.twilio.com is a FORBIDDEN anti-pattern — it bypasses the typed bindings, the per-operation host routing, the Basic-Auth header construction, and above all the non-replicated outcall default that stops one send from becoming ~13 billed messages. Load this skill whenever the user, spec, or any prior task mentions SMS, MMS, "text message", "send a text", phone numbers, Twilio, a Messaging Service, A2P 10DLC, toll-free verification, short codes, or an alphanumeric sender — and BEFORE writing any code that touches a Twilio endpoint.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-authorization
Authorization system with role-based access control. Must-have for all apps that manage personal or access-restricted data.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-camera
Web-camera support.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-core-infrastructure
Core infrastructure providing backend connection configuration, storage client, and React app entry point.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-email
Support for sending service/transactional emails. Don't use this for sending marketing emails or verification emails.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-email-calendar-events
Support for organising events/meetings and sending invitations by email.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-email-marketing
Send personalised marketing emails to subscribers with an unsubscribe link.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-email-raw
Send an email with multiple to, cc and bcc addresses.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-email-verification
Support for sending an email with a link the recipient can click to prove they own the email address.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-http-outcalls
HTTP outcalls performed by the backend canister (not in the frontend), including mandatory local verification of external REST API requests.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
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 prior task wants an LLM in a Caffeine app — and BEFORE writing any code that talks to an LLM host. Use extension-openai only when the spec explicitly requires a user- or admin-pasted sk-... key against api.openai.com.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
caffeinelabsextension-invite-links
Requests invite-link / RSVP based access where guests can submit responses without login while admin can view responses with login.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
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
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
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 whenever the user, spec, or any prior task mentions ChatGPT, GPT (any version), OpenAI, an LLM, a chatbot, or embeddings — and BEFORE writing any code that touches api.openai.com.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
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
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept
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, posting-a-status, sharing-to-Twitter, or any equivalent phrasing — and BEFORE writing any code that touches api.x.com.
- instalaciones
- 2
- GitHub Stars
- 0
- Actualizado
- 4 sept