Get API Docs with chub
andrewyng/context-hub
Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.
Prepares a Twenty app for npm or marketplace release: package metadata, defineApplication listing fields, README and About copy, logo, screenshots and public assets.
Install Twenty App Publishing
$ npx skills add twentyhq/twenty --skill publish-app -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install twentyhq/twenty publish-app --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/twentyhq/twenty.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/twenty-agent-skills/skills/publish-app .claude/skills/publish-app && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "publish-app" agent skill from https://github.com/twentyhq/twenty/tree/main/packages/twenty-agent-skills/skills/publish-app into .claude/skills/publish-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-app", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/twentyhq/twenty/tree/main/packages/twenty-agent-skills/skills/publish-appType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add twentyhq/twenty --skill publish-app -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install twentyhq/twenty publish-app --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/twentyhq/twenty.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/twenty-agent-skills/skills/publish-app .agents/skills/publish-app && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "publish-app" agent skill from https://github.com/twentyhq/twenty/tree/main/packages/twenty-agent-skills/skills/publish-app into .agents/skills/publish-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-app", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add twentyhq/twenty --skill publish-app -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install twentyhq/twenty publish-app --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/twentyhq/twenty.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/twenty-agent-skills/skills/publish-app .cursor/skills/publish-app && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "publish-app" agent skill from https://github.com/twentyhq/twenty/tree/main/packages/twenty-agent-skills/skills/publish-app into .cursor/skills/publish-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-app", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/twentyhq/twenty.git --path packages/twenty-agent-skills/skills/publish-app--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add twentyhq/twenty --skill publish-app -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install twentyhq/twenty publish-app --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/twentyhq/twenty.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/twenty-agent-skills/skills/publish-app .gemini/skills/publish-app && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "publish-app" agent skill from https://github.com/twentyhq/twenty/tree/main/packages/twenty-agent-skills/skills/publish-app into .gemini/skills/publish-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-app", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install twentyhq/twenty publish-appInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add twentyhq/twenty --skill publish-app -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/twentyhq/twenty.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/twenty-agent-skills/skills/publish-app .github/skills/publish-app && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "publish-app" agent skill from https://github.com/twentyhq/twenty/tree/main/packages/twenty-agent-skills/skills/publish-app into .github/skills/publish-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-app", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add twentyhq/twenty --skill publish-app -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install twentyhq/twenty publish-app --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/twentyhq/twenty.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/twenty-agent-skills/skills/publish-app .opencode/skills/publish-app && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "publish-app" agent skill from https://github.com/twentyhq/twenty/tree/main/packages/twenty-agent-skills/skills/publish-app into .opencode/skills/publish-app/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-app", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
publish-app- GitHub stars
- 58k
- Token cost
- ~745 tokens
- SKILL.md length
- 350 words
- Files
- 2
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Prepares a Twenty app for npm or marketplace release: package metadata, defineApplication listing fields, README and About copy, logo, screenshots and public assets.
- Preparing a Twenty app for the marketplace
- Calls yarn; reaches docs.twenty.com
- Writing the README or About text for a Twenty app listing
- Adding a logo, screenshots and marketplace metadata to defineApplication
What it does
Pick this when an existing Twenty app has to look right before it goes public. The agent inspects package.json, README.md, src/application-config.ts and the public folder, then checks that the package carries a bumped version and the twenty-app keyword. Inside defineApplication() it verifies the listing fields: displayName, description, author, category, logoUrl, screenshots, aboutDescription, websiteUrl, termsUrl, emailSupport and issueReportUrl.
logoUrl and screenshots must point at files in public, which must hold no secrets, customer records or unreleased material. If aboutDescription is left out, the marketplace falls back to the npm README, and the About tab renders plain markdown only, with no images or raw HTML. Validation runs with yarn twenty dev:build and publishing with yarn twenty app:publish. Scaffolding, entity changes, private deployments and workspace queries are left to other skills.
When your agent uses it
- Preparing a Twenty app for the marketplace
- Writing the README or About text for a Twenty app listing
- Adding a logo, screenshots and marketplace metadata to defineApplication
- Reviewing a listing before shipping a new version to npm
Example prompts
- “Get my Twenty app ready for the marketplace and check its defineApplication fields.”
- “Write the README for my Twenty app and make sure the About text renders as plain markdown.”
- “Bump the version and publish my Twenty app to npm after checking the public folder for private data.”
Requirements
- A Twenty app project with package.json and src/application-config.ts
- Yarn with the twenty CLI for dev:build and app:publish
What it can do on your machine
Read from SKILL.md and the folder at commit 22ada84. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
yarn
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
docs.twenty.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Twenty App Publishing loads about 745 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 350 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 350 words (~745 tokens).
“Pick this skill when the user wants to make an existing Twenty app presentable — listing copy, branding, public assets, and publication. Representative triggers:”
- name
- publish-app
Files
SKILL.md and 1 other file in packages/twenty-agent-skills/skills/publish-app of twentyhq/twenty.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 22ada84
Compare with similar skills
Twenty App Publishing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Twenty App Publishing this skilltwentyhq/twenty | 58k | — | ~745 | Automated safety check: Pass | Custom licence | |
| Get API Docs with chubandrewyng/context-hub | 14k | 1 repos | ~775 | Automated safety check: Pass | MIT | |
| Update .NET Supported OS Matrixdotnet/core | 22k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Ccb GitHubSeemSeam/claude_codex_bridge | 3.6k | — | ~4.9k | Automated safety check: Pass | Custom licence | |
| README Badges and Headersjal-co/shieldcn | 919 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Release Managerukorvl/lightweight-charts-react-components | 137 | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
- Official
Update .NET Supported OS Matrix
dotnet/core
Audits and updates the supported-os.json files for .NET releases, checking them against upstream lifecycle data and regenerating the markdown with the release-notes tool.
Ccb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
README Badges and Headers
jal-co/shieldcn
Adds shadcn/ui-styled README badges, badge groups, download charts, header banners and sponsor or contributor grids using the shieldcn service.
Release Manager
ukorvl/lightweight-charts-react-components
Prepare or finalize semver releases for this repository. An agent skill from ukorvl/lightweight-charts-react-components.
Verify New Sample PR
pnp/sp-dev-fx-aces
Verify a "new sample" PR in pnp/sp-dev-fx-aces builds successfully, then produce a deployment + testing checklist from the sample README so it can be manually deployed and tested before merging.
More from twentyhq/twenty
All 13 skills in this repoTwenty App Entity Development
twentyhq/twenty
Guides changes to an existing Twenty app: adding or editing objects, layouts, logic functions and front components, with a plan stated before multi-entity edits.
Twenty App Operations
twentyhq/twenty
Operates an existing Twenty app: managing remotes, syncing, building, deploying, reading logs, running tests and setting up CI/CD, with confirmation for production.
Twenty Syncable Entity Validation
twentyhq/twenty
Contributor guide for step three of adding a syncable entity to the Twenty server: write the validator, the migration action builder and the orchestrator wiring.
Twenty Syncable Entity Cache and Transform
twentyhq/twenty
Walks through step 2 of adding a syncable entity to the Twenty server: a cache service for flat entity maps and utilities that transform entities and DTOs into universal flat entities.
Twenty Syncable Entity Wiring
twentyhq/twenty
Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server.
Twenty Entity Runner Actions
twentyhq/twenty
Step four of adding a syncable entity in the Twenty server: write create, update and delete action handlers that run workspace migrations against the database.
Related
Works with
Categories
Questions about Twenty App Publishing
What does Twenty App Publishing do?
Prepares a Twenty app for npm or marketplace release: package metadata, defineApplication listing fields, README and About copy, logo, screenshots and public assets. Pick this when an existing Twenty app has to look right before it goes public.ts and the public folder, then checks that the package carries a bumped version and the twenty-app keyword.
When should I use Twenty App Publishing?
Twenty App Publishing fits situations like: preparing a Twenty app for the marketplace; writing the README or About text for a Twenty app listing; adding a logo, screenshots and marketplace metadata to defineApplication; reviewing a listing before shipping a new version to npm.
How do I install Twenty App Publishing in Claude Code?
Run `npx skills add twentyhq/twenty --skill publish-app -a claude-code`. Or copy the skill folder (packages/twenty-agent-skills/skills/publish-app in twentyhq/twenty) into .claude/skills/publish-app in your project. Claude Code loads it when a task matches its description.
How do I install Twenty App Publishing in Codex?
Run `npx skills add twentyhq/twenty --skill publish-app -a codex`. Or copy the skill folder (packages/twenty-agent-skills/skills/publish-app in twentyhq/twenty) into .agents/skills/publish-app in your project. Codex loads it when a task matches its description.
Can I use Twenty App Publishing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add twentyhq/twenty --skill publish-app -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publish-app, .gemini/skills/publish-app, .github/skills/publish-app and .opencode/skills/publish-app in your project.
What does Twenty App Publishing need to run?
Going by SKILL.md and its folder, Twenty App Publishing needs the command-line tools its instructions call (yarn). Our summary lists: A Twenty app project with package.json and src/application-config.ts; Yarn with the twenty CLI for dev:build and app:publish.
Does Twenty App Publishing access the network?
SKILL.md names 1 domain. In commands or code: docs.twenty.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Twenty App Publishing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Twenty App Publishing use?
Twenty App Publishing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Twenty App Publishing use?
About 745 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Twenty App Publishing?
Skills that share tags, products or a category with Twenty App Publishing: Get API Docs with chub (andrewyng/context-hub, 14k stars), Update .NET Supported OS Matrix (dotnet/core, 22k stars), Ccb GitHub (SeemSeam/claude_codex_bridge, 3.6k stars) and README Badges and Headers (jal-co/shieldcn, 919 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Twenty App Publishing?
twentyhq (a GitHub organization) maintains it in twentyhq/twenty, which has 58,192 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 11, 2026.
Source: twentyhq/twenty on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.