connected-apps

Étoiles14

Forks3

Mis à jour19 juillet 2026 à 07:31

Uses the user's connected Gmail, GitHub, Notion, Google Workspace, Slack, and other supported accounts for explicit on-demand actions. Use when the user asks Cheatcode to read, search, create, or update something in a connected service.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

cheatcode-ai

cheatcode-ai/cheatcode

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	connected-apps
description	Uses the user's connected Gmail, GitHub, Notion, Google Workspace, Slack, and other supported accounts for explicit on-demand actions. Use when the user asks Cheatcode to read, search, create, or update something in a connected service.
category	Builder & Apps
tags	integrations, composio, oauth, connected apps
license	MIT
compatibility	Requires an account connected from the Cheatcode Skills screen and the Composio runtime tools.

Connected Apps

Perform the user's requested action through their connected account. This playbook is for agent-side work now; it does not add provider credentials or deployable integration code to a generated application.

Workflow

Identify the provider, intended action, target object, and whether the operation mutates external state.
Call composio_list_tools with the provider and a focused search term to discover the exact supported action.
If the list is truncated, narrow the search rather than guessing a tool slug.
Call composio_execute only for the explicit action the user requested.
Verify the returned identifier, status, or content before reporting success.

Rules

Do not call a connected app merely because one is available.
Prefer read-only discovery before writes when the target is ambiguous.
Never claim an account is connected when the tool reports that authorization is missing. Direct the user to the Skills screen to connect it.
Do not place OAuth tokens, provider secrets, or Cheatcode backend credentials in project files, browser code, logs, or chat.
Do not generate app-side integration routes that depend on Cheatcode's private Composio runtime.
For sending, deleting, publishing, inviting, purchasing, or permission changes, confirm the target and scope from the user's request before executing.

Verification

A read action returns the requested object or a clear not-found result.
A write action returns a provider-side identifier or confirmed final state.
The summary names what changed and where without exposing internal tool payloads.

Plus depuis ce dépôt

même dépôt

skill-authoring

cheatcode-ai/cheatcode

Create or update project-local Cheatcode skills for direct backend routes, local workflows, or non-Composio external APIs. This is the default skill authoring path.

2026-07-1914

manage-skills

cheatcode-ai/cheatcode

Inspect and manage globally enabled Cheatcode tools and integrations.

2026-07-1914

browser-use

cheatcode-ai/cheatcode

Browser automation CLI for the Cheatcode coding agent. Use when the user needs to interact with websites, take screenshots, fill forms, click elements, navigate pages, or automate any browser task.

2026-07-1914

canvas-design

cheatcode-ai/cheatcode

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

2026-07-1914

docx

cheatcode-ai/cheatcode

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

2026-07-1914

file-reading

cheatcode-ai/cheatcode

Use this skill when you need to read a file whose content is NOT already in your context — you only know its path. This skill is a router: it tells you which tool to use for each file type (pdf, docx, xlsx, csv, json, images, archives, ebooks) so you read the right amount the right way instead of blindly running cat on a binary. Do NOT use this skill if the file content is already visible in your context — you already have it.

2026-07-1914

Connected Apps

Workflow

Identify the provider, intended action, target object, and whether the operation mutates external state.

Call composio_list_tools with the provider and a focused search term to discover the exact supported action.

If the list is truncated, narrow the search rather than guessing a tool slug.

Call composio_execute only for the explicit action the user requested.

Verify the returned identifier, status, or content before reporting success.

Rules

Do not call a connected app merely because one is available.

Prefer read-only discovery before writes when the target is ambiguous.

Never claim an account is connected when the tool reports that authorization is missing. Direct the user to the Skills screen to connect it.

Do not place OAuth tokens, provider secrets, or Cheatcode backend credentials in project files, browser code, logs, or chat.

Do not generate app-side integration routes that depend on Cheatcode's private Composio runtime.

For sending, deleting, publishing, inviting, purchasing, or permission changes, confirm the target and scope from the user's request before executing.

Verification

A read action returns the requested object or a clear not-found result.

A write action returns a provider-side identifier or confirmed final state.

The summary names what changed and where without exposing internal tool payloads.