ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
A skill your agent uses when contributing to InsForge's product documentation in this repository.
Install Docs
$ npx skills add InsForge/InsForge --skill docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install InsForge/InsForge docs --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/InsForge/InsForge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/insforge-dev/docs .claude/skills/docs && 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 "docs" agent skill from https://github.com/InsForge/InsForge/tree/main/.codex/skills/insforge-dev/docs into .claude/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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/InsForge/InsForge/tree/main/.codex/skills/insforge-dev/docsType 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 InsForge/InsForge --skill docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install InsForge/InsForge docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InsForge/InsForge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/insforge-dev/docs .agents/skills/docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs" agent skill from https://github.com/InsForge/InsForge/tree/main/.codex/skills/insforge-dev/docs into .agents/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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 InsForge/InsForge --skill docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install InsForge/InsForge docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InsForge/InsForge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/insforge-dev/docs .cursor/skills/docs && 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 "docs" agent skill from https://github.com/InsForge/InsForge/tree/main/.codex/skills/insforge-dev/docs into .cursor/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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/InsForge/InsForge.git --path .codex/skills/insforge-dev/docs--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 InsForge/InsForge --skill docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install InsForge/InsForge docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InsForge/InsForge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/insforge-dev/docs .gemini/skills/docs && 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 "docs" agent skill from https://github.com/InsForge/InsForge/tree/main/.codex/skills/insforge-dev/docs into .gemini/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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 InsForge/InsForge docsInstalls 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 InsForge/InsForge --skill docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/InsForge/InsForge.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/insforge-dev/docs .github/skills/docs && 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 "docs" agent skill from https://github.com/InsForge/InsForge/tree/main/.codex/skills/insforge-dev/docs into .github/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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 InsForge/InsForge --skill docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install InsForge/InsForge docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/InsForge/InsForge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/insforge-dev/docs .opencode/skills/docs && 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 "docs" agent skill from https://github.com/InsForge/InsForge/tree/main/.codex/skills/insforge-dev/docs into .opencode/skills/docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs", 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
docs- GitHub stars
- 13k
- Token cost
- ~761 tokens
- SKILL.md length
- 342 words
- Files
- 2
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when contributing to InsForge's product documentation in this repository.
- Works in 3 steps: Put each document in the correct… → Match the writing style to the audience. → Prevent documentation drift on every…
- Contributing to InsForges product documentation in this repository
- SKILL.md covers Scope, Working Rules and Validation
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Docs is an agent skill from InsForge/InsForge. Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in docs/core-concepts, agent docs in .agents/docs, SDK integration guides in docs/sdks, and OpenAPI specs in openapi.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `DOCS_I18N.md`).
It sits in Backend & APIs, covering OpenAPI specifications, Third-party API integration and Technical writing. It works with OpenAPI. The repository describes itself as: The all-in-one, open-source backend platform for agentic coding. InsForge gives your coding agent database, auth, storage, compute, hosting, and AI gateway to ship full-stack… The licence is Apache-2.0.
When your agent uses it
- Contributing to InsForges product documentation in this repository
- Tasks that involve OpenAPI specifications
- Tasks that involve Third-party API integration
Example prompts
- “/docs”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Put each document in the correct documentation surface.
- Match the writing style to the audience.
- Prevent documentation drift on every implementation change.
What it can do on your machine
Read from SKILL.md and the folder at commit 2ec64b6. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Docs loads about 761 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 342 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
The full file from InsForge/InsForge at commit 2ec64b6, republished under its Apache-2.0 licence (© InsForge). 342 words, ~761 tokens.
Download SKILL.mdSave it as
.claude/skills/docs/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- docs
- description
- Use this skill when contributing to InsForge's product documentation in this repository. This is for maintainers editing public docs in `docs/core-concepts`, agent docs in `.agents/docs`, SDK integration guides in `docs/sdks`, and OpenAPI specs in `openapi`.
InsForge Dev Docs
Use this skill for docs/core-concepts/, .agents/docs/, docs/sdks/, and openapi/ in the InsForge repository.
The documentation in this repo is primarily product documentation for InsForge users and agents integrating with InsForge. This skill is for InsForge engineers maintaining that public documentation surface.
Scope
docs/core-concepts/**.agents/docs/**docs/sdks/**openapi/**
Working Rules
Put each document in the correct documentation surface.
- Human-friendly docs published on the public doc site belong in
docs/core-concepts/and related public doc folders. - For implementation-heavy public docs, prefer an
architecture.mdfile inside the relevantdocs/core-concepts/<domain>/folder. - Agent-only instructions belong in
.agents/docs/. - SDK integration guides for each framework belong in
docs/sdks/. - OpenAPI contract changes belong in the matching files under
openapi/.
- Human-friendly docs published on the public doc site belong in
Match the writing style to the audience.
- Public docs should be human-friendly and explain the implementation clearly.
- Keep public docs human-sounding: avoid AI-writing tells such as em dashes, rule-of-three lists, "not just X but Y" parallelism, inflated significance, vague attribution, and AI vocabulary (delve, leverage, underscore, seamless, robust). See the
doc-authorskill'sINSFORGE.mdoverlay, "Sound human, not AI-generated". architecture.mdpages indocs/core-concepts/should explain how the feature works in detail.- Agent docs in
.agents/docs/should be instruction-first and execution-oriented. - Agent docs should avoid explanatory filler and focus on the exact steps an agent should follow to complete the work.
Prevent documentation drift on every implementation change.
- Before changing implementation, check the current user-facing docs for that feature.
- After changing implementation, update the relevant Markdown docs and the relevant OpenAPI YAML files in the same pass.
- Do not treat OpenAPI and Markdown as separate optional follow-ups when the feature contract or behavior changed.
- If a change affects agent workflows, update the corresponding file in
.agents/docs/. - If a change affects public product understanding, update the corresponding file in
docs/core-concepts/, includingarchitecture.mdwhen implementation details changed. - If a change affects SDK integration guidance, update the corresponding framework guide in
docs/sdks/.
Validation
- Re-read every documented command, path, route, and payload for correctness.
- Cross-check OpenAPI YAML and Markdown docs against the implemented behavior before finishing.
- Mention anything you could not verify directly.
© InsForge, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .codex/skills/insforge-dev/docs of InsForge/InsForge.
- SKILL.md
- DOCS_I18N.md
Open the folder on GitHubat commit 2ec64b6
Compare with similar skills
Docs 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 |
|---|---|---|---|---|---|---|
| Docs this skillInsForge/InsForge | 13k | — | ~761 | Automated safety check: Pass | Apache-2.0 | |
| ToolJet Marketplace Plugin BuilderToolJet/ToolJet | 41k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| OpenAPI CLI CallerEvilFreelancer/openapi-to-cli | 265 | — | ~879 | Automated safety check: Pass | MIT | |
| Soundcloud API Integrationsoundcloud/api | 257 | — | ~787 | Automated safety check: Pass | None | |
| Mock REST APIsmendixlabs/mxcli | 128 | 1 repos | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| REST Clientmendixlabs/mxcli | 128 | 1 repos | ~3.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
OpenAPI CLI Caller
EvilFreelancer/openapi-to-cli
Turns an OpenAPI, Swagger or OpenRPC spec into CLI commands the agent can search and call, with no MCP server or code generation.
Soundcloud API Integration
soundcloud/api
Integrates applications with the SoundCloud HTTP API using OAuth 2.1, OpenAPI, and developer docs.
Mock REST APIs
mendixlabs/mxcli
Stand up an HTTP endpoint you control instead of a live third-party API, and point the Mendix app at it — Prism from an OpenAPI contract, a constant swap, or a forward proxy.
REST Client
mendixlabs/mxcli
Call external REST APIs from Mendix — the three approaches (inline REST CALL, consumed REST client document, generated from OpenAPI) and how to choose.
E2a Integrate
tokencanopy/e2a
A skill your agent uses when adding e2a email capabilities to an application or codebase: outbound sending, inbound signed webhooks, REST polling, or SDK integration.
More from InsForge/InsForge
All 8 skills in this repoDoc Author
InsForge/InsForge
Write, edit, and maintain documentation. An agent skill from InsForge/InsForge.
E2E Testing
InsForge/InsForge
A skill your agent uses when an InsForge maintainer has finished an OSS repo change and is ready to open, update, or submit the InsForge PR.
Backend
InsForge/InsForge
A skill your agent uses when contributing to InsForge's backend package.
Dashboard
InsForge/InsForge
A skill your agent uses when contributing to InsForge's shared dashboard package.
Insforge Dev
InsForge/InsForge
Use this skill set when contributing to the InsForge monorepo itself.
Shared Schemas
InsForge/InsForge
A skill your agent uses when contributing to InsForge's shared schema package.
Related
Works with
Categories
Questions about Docs
What does Docs do?
A skill your agent uses when contributing to InsForge's product documentation in this repository. Docs is an agent skill from InsForge/InsForge. Use this skill when contributing to InsForge's product documentation in this repository.
When should I use Docs?
Docs fits situations like: contributing to InsForges product documentation in this repository; tasks that involve OpenAPI specifications; tasks that involve Third-party API integration.
How do I install Docs in Claude Code?
Run `npx skills add InsForge/InsForge --skill docs -a claude-code`. Or copy the skill folder (.codex/skills/insforge-dev/docs in InsForge/InsForge) into .claude/skills/docs in your project. Claude Code loads it when a task matches its description.
How do I install Docs in Codex?
Run `npx skills add InsForge/InsForge --skill docs -a codex`. Or copy the skill folder (.codex/skills/insforge-dev/docs in InsForge/InsForge) into .agents/skills/docs in your project. Codex loads it when a task matches its description.
Can I use Docs 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 InsForge/InsForge --skill docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs, .gemini/skills/docs, .github/skills/docs and .opencode/skills/docs in your project.
What does Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs is instructions for the agent only.
Does Docs access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Docs 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 Docs use?
Docs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docs use?
About 761 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 Docs?
Skills that share tags, products or a category with Docs: ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars), OpenAPI CLI Caller (EvilFreelancer/openapi-to-cli, 265 stars), Soundcloud API Integration (soundcloud/api, 257 stars) and Mock REST APIs (mendixlabs/mxcli, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs?
InsForge (a GitHub organization) maintains it in InsForge/InsForge, which has 13,064 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.
Source: InsForge/InsForge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.