LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
A skill your agent uses when working with Frappe Cloud, Press API, provisioning sites, or managing benches on Frappe Cloud infrastructure.
Install Frappe Ops Cloud
$ npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-ops-cloud --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/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/source/ops/frappe-ops-cloud .claude/skills/frappe-ops-cloud && 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 "frappe-ops-cloud" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-cloud into .claude/skills/frappe-ops-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-ops-cloud", 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/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-cloudType 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 Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-ops-cloud --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/source/ops/frappe-ops-cloud .agents/skills/frappe-ops-cloud && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frappe-ops-cloud" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-cloud into .agents/skills/frappe-ops-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-ops-cloud", 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 Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-ops-cloud --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/source/ops/frappe-ops-cloud .cursor/skills/frappe-ops-cloud && 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 "frappe-ops-cloud" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-cloud into .cursor/skills/frappe-ops-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-ops-cloud", 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/Impertio-Studio/Frappe_Claude_Skill_Package.git --path skills/source/ops/frappe-ops-cloud--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 Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-ops-cloud --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/source/ops/frappe-ops-cloud .gemini/skills/frappe-ops-cloud && 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 "frappe-ops-cloud" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-cloud into .gemini/skills/frappe-ops-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-ops-cloud", 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 Impertio-Studio/Frappe_Claude_Skill_Package frappe-ops-cloudInstalls 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 Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/source/ops/frappe-ops-cloud .github/skills/frappe-ops-cloud && 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 "frappe-ops-cloud" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-cloud into .github/skills/frappe-ops-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-ops-cloud", 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 Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Impertio-Studio/Frappe_Claude_Skill_Package frappe-ops-cloud --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/source/ops/frappe-ops-cloud .opencode/skills/frappe-ops-cloud && 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 "frappe-ops-cloud" agent skill from https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package/tree/main/skills/source/ops/frappe-ops-cloud into .opencode/skills/frappe-ops-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frappe-ops-cloud", 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
frappe-ops-cloud- GitHub stars
- 188
- Token cost
- ~3k tokens
- SKILL.md length
- 1,261 words
- Files
- 4 (incl. references)
- Skills in repo
- 61
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when working with Frappe Cloud, Press API, provisioning sites, or managing benches on Frappe Cloud infrastructure.
- Works in 5 steps: Navigate to Apps in the Frappe Cloud… → Click Add App and provide the GitHub… → Select the branch to deploy → …
- Working with Frappe Cloud
- SKILL.md covers Quick Reference: Frappe Cloud…, Decision Tree: Frappe Cloud vs…, Frappe Cloud Overview and Frappe Cloud Dashboard, plus 5 more sections
- Reaches github.com
What it does
Frappe Ops Cloud is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when working with Frappe Cloud, Press API, provisioning sites, or managing benches on Frappe Cloud infrastructure. Prevents failed deployments from misconfigured cloud settings and API misuse. Covers Frappe Cloud dashboard, Press API, site provisioning, bench management, environment variables, cloud-specific limitations. Keywords: Frappe Cloud, Press, cloud API, site provisioning, bench management, FC, frappecloud, Frappe Cloud deploy, FC hosting, cloud setup, managed hosting..
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/anti-patterns.md` and `references/examples.md`). Compatibility notes: Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
It sits in DevOps & Cloud, covering Deployment and Secrets management. The repository describes itself as: 60 deterministic Claude AI skills for Frappe Framework & ERPNext v14-v16 development and operations. The licence is MIT.
When your agent uses it
- Working with Frappe Cloud
- Provisioning sites
- Managing benches on Frappe Cloud infrastructure
Example prompts
- “/frappe-ops-cloud”
Requirements
- Docker
- Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Navigate to Apps in the Frappe Cloud dashboard
- Click Add App and provide the GitHub repository URL
- Select the branch to deploy
- Configure build settings if needed
- The app becomes available for installation on sites within compatible benches
What it can do on your machine
Read from SKILL.md and the folder at commit 36cfa80. 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
Hosts in commands or code, which the agent is likely to contact:
github.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.
Compatibility
Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
From compatibility in the SKILL.md frontmatter.
Context cost
Frappe Ops Cloud loads about 3k tokens when it runs, and up to ~5.4k if it reads all its reference files. Until then it costs about 126 tokens; SKILL.md has 1,261 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 Impertio-Studio/Frappe_Claude_Skill_Package at commit 36cfa80, republished under its MIT licence (© Impertio-Studio). 1,261 words, ~3,025 tokens.
Download SKILL.mdSave it as
.claude/skills/frappe-ops-cloud/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- frappe-ops-cloud
- description
- Use when working with Frappe Cloud, Press API, provisioning sites, or managing benches on Frappe Cloud infrastructure. Prevents failed deployments from misconfigured cloud settings and API misuse. Covers Frappe Cloud dashboard, Press API, site provisioning, bench management, environment variables, cloud-specific limitations. Keywords: Frappe Cloud, Press, cloud API, site provisioning, bench management, FC, frappecloud, Frappe Cloud deploy, FC hosting, cloud setup, managed hosting..
- compatibility
- Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16.
- license
- MIT
- metadata.author
- OpenAEC-Foundation
- metadata.version
- 2.0
Frappe Cloud & Press
Complete reference for Frappe Cloud managed hosting and Press self-hosted alternative.
Quick Reference: Frappe Cloud Concepts
| Concept | Description |
|---|---|
| Site | A single Frappe instance with its own database, domain, and apps |
| Bench | A shared runtime environment hosting one or more sites with the same app versions |
| Server | The underlying infrastructure (VM) running one or more benches |
| Private Bench | A dedicated bench for a single customer with full control |
| Shared Bench | A Frappe-managed bench shared across multiple sites |
| Press | The open-source platform (AGPL-3.0) that powers Frappe Cloud |
| Agent | Flask application on each server enabling Press-to-site communication |
Decision Tree: Frappe Cloud vs Self-Hosted
Choosing hosting strategy:
├── Small team, want zero ops overhead?
│ └── Frappe Cloud (Shared Bench) — fastest time to production
├── Need custom server configuration?
│ ├── Budget for managed infra? → Frappe Cloud (Private Bench)
│ └── Want full control? → Self-hosted with bench
├── Need to host Frappe for multiple clients?
│ ├── Want managed platform? → Frappe Cloud
│ └── Want own platform? → Self-hosted Press
├── Regulatory/compliance — data must stay on-premises?
│ └── Self-hosted (bench or Press)
└── Development/testing environment?
├── Quick prototype → Frappe Cloud (free trial)
└── Long-term dev → Local bench installationFrappe Cloud Overview
Frappe Cloud is a fully managed hosting platform for the Frappe stack. It handles server provisioning, backups, updates, monitoring, and scaling.
Core Features
| Feature | Details |
|---|---|
| Automated backups | Scheduled daily backups with retention policies |
| Automatic updates | Managed update cycles for Frappe apps |
| Scaling | Horizontal and vertical scaling without downtime |
| Multi-tenancy | Multiple independent sites per bench |
| SSL/TLS | Automatic certificate provisioning and renewal |
| Monitoring | Real-time server and site monitoring |
| Role-based access | Granular permissions for team members |
| Billing | Daily/monthly subscriptions, wallet credits, multiple payment methods |
Infrastructure Options
| Option | Use Case |
|---|---|
| Shared Bench | Cost-effective for small sites; Frappe manages the bench |
| Private Bench | Dedicated environment; custom app versions and update schedules |
| Dedicated Server | Full server for high-traffic or compliance requirements |
Frappe Cloud Dashboard
Site Management
The dashboard provides centralized control for all site operations:
- Create sites — Provision new sites on shared or private benches
- Install/remove apps — Add or remove Frappe apps from sites
- Backups — Manual and scheduled backups, restore from backup
- Domain management — Add custom domains with automatic SSL
- Site config — Edit
site_config.jsonvia the dashboard - Monitoring — View CPU, memory, disk usage, and request logs
- Site actions — Migrate, update, suspend, archive, or transfer sites
Bench Management
- Create benches — Set up shared or private benches
- App management — Select apps and their versions/branches
- Update scheduling — Control when benches receive updates
- Environment variables — Set custom environment variables
- SSH access — Connect to bench via SSH for debugging
- Log browser — View application and error logs
- Database access — Query the database via the dashboard
Server Management
- Provision servers — Create servers across multiple cloud providers
- Scale resources — Upgrade CPU, memory, and storage
- Storage add-ons — Attach additional storage volumes
- Server snapshots — Create and restore server snapshots
Deploying Apps on Frappe Cloud
Adding a Custom App
- Navigate to Apps in the Frappe Cloud dashboard
- Click Add App and provide the GitHub repository URL
- Select the branch to deploy
- Configure build settings if needed
- The app becomes available for installation on sites within compatible benches
App Marketplace
Frappe Cloud includes a marketplace where developers can:
- List apps with descriptions and pricing
- Set compatibility requirements (Frappe version, dependencies)
- Configure pricing models (free, one-time, subscription)
- Manage payouts for commercial apps
- Track installations and usage analytics
Deployment Workflow
Developer pushes code → Frappe Cloud detects update →
Bench rebuild triggered → Assets compiled →
Sites migrated → New version liveFor Private Benches: Updates are controlled by the bench owner — NEVER auto-deployed without approval.
For Shared Benches: Frappe manages the update schedule.
Site Provisioning Workflow
Creating a New Site
- Select bench — Choose shared or private bench
- Choose plan — Select resource allocation (CPU, memory, storage)
- Configure apps — Select which apps to install
- Set domain — Use
*.frappe.cloudsubdomain or custom domain - Create — Frappe Cloud provisions the site (typically under 5 minutes)
Custom Domain Setup
- Navigate to site Domains in the dashboard
- Add your custom domain (e.g.,
erp.example.com) - Configure DNS: Add a CNAME record pointing to the Frappe Cloud proxy
- Frappe Cloud verifies DNS and provisions SSL certificate automatically
- ALWAYS wait for DNS propagation before expecting SSL to work (up to 48 hours)
Critical Rules
- ALWAYS use CNAME records for custom domains (not A records)
- NEVER transfer DNS to Frappe Cloud — only add CNAME records
- ALWAYS verify SSL is active before switching production traffic
- Custom domain SSL uses Let's Encrypt — auto-renews before expiry
Frappe Cloud vs Self-Hosted Comparison
| Aspect | Frappe Cloud | Self-Hosted (bench) | Self-Hosted (Press) |
|---|---|---|---|
| Setup time | Minutes | Hours | Days |
| Server management | Managed | You manage | You manage |
| Backups | Automatic | Manual/cron | Automatic |
| Updates | Managed schedule | bench update | Managed via Press |
| SSL certificates | Automatic | Manual/certbot | Automatic |
| Scaling | Dashboard button | Manual | Dashboard |
| Multi-tenancy | Built-in | DNS multi-tenant | Built-in |
| Cost | Subscription | Infrastructure only | Infrastructure only |
| Custom server config | Limited | Full control | Full control |
| Data sovereignty | Frappe's infra | Your infra | Your infra |
| SSH access | Private bench only | Full | Full |
| Monitoring | Built-in | Set up yourself | Built-in |
| Support | Included | Community only | Community only |
Press: Self-Hosted Frappe Cloud
What Is Press?
Press is the open-source platform (AGPL-3.0) that powers Frappe Cloud. Organizations can self-host Press to create their own managed hosting platform for Frappe applications.
GitHub: https://github.com/frappe/press
Show full SKILL.md (495 more words)Show less
Architecture
| Component | Technology | Role |
|---|---|---|
| Press | Frappe Framework | Platform management, billing, dashboard |
| Agent | Flask | Server-to-site communication |
| Docker | Container runtime | App packaging and deployment |
| Ansible | Automation | Server provisioning and configuration |
| Frappe UI | Vue.js | Dashboard frontend |
Key Capabilities
- Multi-server management — Provision and manage multiple servers
- Site lifecycle — Create, update, migrate, backup, restore, archive sites
- Bench management — Deploy benches with specific app versions
- Billing system — Subscriptions, invoicing, wallet credits, ERP integration
- Marketplace — App listing, pricing, payouts
- Role-based access — Granular permissions per team and resource
- Monitoring — Real-time metrics and alerting
When to Self-Host Press
- You need to host Frappe for multiple clients/tenants
- You want a managed platform but on your own infrastructure
- You need full data sovereignty and regulatory compliance
- You want to offer Frappe hosting as a service
When NOT to Self-Host Press
- NEVER self-host Press for a single site — use bench directly
- NEVER self-host Press without dedicated DevOps capacity
- NEVER underestimate the operational overhead — Press itself requires maintenance
Self-Hosting Requirements
- Dedicated servers (bare metal or VMs) with Ubuntu
- DNS management for wildcard domains
- Object storage for backups (S3-compatible)
- SMTP service for transactional email
- Familiarity with Ansible, Docker, and Frappe Framework
Frappe Cloud Limitations
What You CANNOT Do on Frappe Cloud
- Install system-level packages (no root access on shared benches)
- Modify Nginx/Supervisor configuration directly
- Access raw database files (only SQL access via dashboard)
- Run long-running background processes outside Frappe's job queue
- Use non-standard ports or protocols
Shared Bench Limitations
- No SSH access
- No custom environment variables (use site_config.json instead)
- Shared resources with other sites — performance may vary
- Update schedule controlled by Frappe (not the site owner)
Private Bench Advantages Over Shared
- SSH access for debugging
- Custom environment variables
- Controlled update schedule
- Dedicated resources
- Custom app versions and branches
Frappe Cloud Best Practices
Site Configuration
- ALWAYS set
maintenance_modebefore large data imports - ALWAYS use the dashboard for site config changes (not direct file edits)
- NEVER disable scheduler on Frappe Cloud — use
pause_schedulerinstead - ALWAYS test app updates on a staging site before production
Backup Strategy
- Frappe Cloud creates automatic daily backups
- ALWAYS create a manual backup before major changes
- ALWAYS download and store backups off-platform periodically
- NEVER rely solely on Frappe Cloud backups — maintain your own copies
Performance
- Monitor site usage via the dashboard — upgrade plan before hitting limits
- Use background jobs for heavy operations (not synchronous API calls)
- Enable Redis caching for frequently accessed data
- Review slow query logs via the database analyzer tool
Frappe Cloud DevOps Tools
| Tool | Purpose |
|---|---|
| Log Browser | View application logs, error logs, scheduler logs |
| Database Analyzer | Run SQL queries, view slow queries, analyze indexes |
| Binlog Browser | View database change logs (binary log events) |
| SSH Access | Terminal access to private benches for debugging |
| Process Status | View running workers, scheduler status, job queue |
Analytics Integrations
Frappe Cloud sites can connect to external analytics tools:
- Frappe Insights (native)
- Power BI (via API)
- Metabase (via database connection)
- Custom dashboards (via Frappe API)
Reference Files
| File | Contents |
|---|---|
| examples.md | Cloud deployment workflow examples |
| anti-patterns.md | Common Frappe Cloud mistakes and fixes |
© Impertio-Studio, MIT. 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 3 other files (references) in skills/source/ops/frappe-ops-cloud of Impertio-Studio/Frappe_Claude_Skill_Package.
- SKILL.md
- references/.gitkeep
- references/anti-patterns.md
- references/examples.md
Open the folder on GitHubat commit 36cfa80
Compare with similar skills
Frappe Ops Cloud 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 |
|---|---|---|---|---|---|---|
| Frappe Ops Cloud this skillImpertio-Studio/Frappe_Claude_Skill_Package | 188 | — | ~3k | Automated safety check: Pass | MIT | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Azure Bicep Skilltimothywarner-org/claude-code | 224 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Manage Cloud EnvMentra-Community/MentraOS | 2.4k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Monstermq Broker Configvogler75/monster-mq | 143 | — | ~2.2k | Automated safety check: Pass | GPL-3.0 | |
| Deploymentmatrixorigin/memoria | 609 | — | ~1.6k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Azure Bicep Skill
timothywarner-org/claude-code
A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.
Manage Cloud Env
Mentra-Community/MentraOS
Add or change backend deployment environment variables through Doppler shared configs and native Porter syncs.
Monstermq Broker Config
vogler75/monster-mq
Guide for configuring, deploying, and operating the MonsterMQ broker.
Deployment
matrixorigin/memoria
Deploy Memoria with Docker Compose or Kubernetes. An agent skill from matrixorigin/memoria.
Letta Configuration
letta-ai/skills
Configure LLM models and providers for Letta agents and servers.
More from Impertio-Studio/Frappe_Claude_Skill_Package
All 61 skills in this repoFrappe Ops Website Deploy
Impertio-Studio/Frappe_Claude_Skill_Package
Deploy HTML/CSS websites to ERPNext/Frappe (v15/v16) as Web Pages via the REST API.
Frappe Agent Architect
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when designing multi-app Frappe architectures, deciding whether to split functionality into separate apps, or implementing cross-app communication patterns.
Frappe Agent Debugger
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when debugging Frappe errors, using bench console for live inspection, analyzing tracebacks, or reading Frappe log files.
Frappe Agent Interpreter
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when receiving vague or unclear ERPNext/Frappe development requests that need interpretation.
Frappe Agent Migrator
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when migrating a Frappe app between major versions, detecting breaking API changes, or resolving post-migration errors.
Frappe Agent Validator
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls.
Related
Categories
Questions about Frappe Ops Cloud
What does Frappe Ops Cloud do?
A skill your agent uses when working with Frappe Cloud, Press API, provisioning sites, or managing benches on Frappe Cloud infrastructure. Frappe Ops Cloud is an agent skill from Impertio-Studio/Frappe_Claude_Skill_Package. Use when working with Frappe Cloud, Press API, provisioning sites, or managing benches on Frappe Cloud infrastructure.
When should I use Frappe Ops Cloud?
Frappe Ops Cloud fits situations like: working with Frappe Cloud; provisioning sites; managing benches on Frappe Cloud infrastructure.
How do I install Frappe Ops Cloud in Claude Code?
Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a claude-code`. Or copy the skill folder (skills/source/ops/frappe-ops-cloud in Impertio-Studio/Frappe_Claude_Skill_Package) into .claude/skills/frappe-ops-cloud in your project. Claude Code loads it when a task matches its description.
How do I install Frappe Ops Cloud in Codex?
Run `npx skills add Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a codex`. Or copy the skill folder (skills/source/ops/frappe-ops-cloud in Impertio-Studio/Frappe_Claude_Skill_Package) into .agents/skills/frappe-ops-cloud in your project. Codex loads it when a task matches its description.
Can I use Frappe Ops Cloud 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 Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-ops-cloud -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frappe-ops-cloud, .gemini/skills/frappe-ops-cloud, .github/skills/frappe-ops-cloud and .opencode/skills/frappe-ops-cloud in your project.
What does Frappe Ops Cloud need to run?
SKILL.md names no scripts, command-line tools or credentials: Frappe Ops Cloud is instructions for the agent only. Our summary lists: Docker. Compatibility (from SKILL.md): Claude Code, Claude.ai Projects, Claude API. Frappe v14-v16..
Does Frappe Ops Cloud access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Frappe Ops Cloud 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 Frappe Ops Cloud use?
Frappe Ops Cloud is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Frappe Ops Cloud use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
What are the alternatives to Frappe Ops Cloud?
Skills that share tags, products or a category with Frappe Ops Cloud: LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Azure Bicep Skill (timothywarner-org/claude-code, 224 stars), Manage Cloud Env (Mentra-Community/MentraOS, 2.4k stars) and Monstermq Broker Config (vogler75/monster-mq, 143 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Frappe Ops Cloud?
Impertio-Studio (a GitHub organization) maintains it in Impertio-Studio/Frappe_Claude_Skill_Package, which has 188 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on September 17, 2026.
Source: Impertio-Studio/Frappe_Claude_Skill_Package on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.