Skip to content
Development
Skill

/amplication

Amplication integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amplication data.

From plugin
application-skills
268200 skills
Install
$ npx -y skills add membranedev/application-skills --skill amplication --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/amplication

Context preview

The summary Claude sees to decide when to auto-load this skill.

Amplication integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amplication data.

SKILL.md

amplication.SKILL.md
name: amplication
description: |
  Amplication integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amplication data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""

Amplication

Amplication is an open-source platform that helps developers build Node.js backends without writing code. It's used by developers and teams who want to accelerate backend development and easily manage their data models and APIs.

Official docs: https://docs.amplication.com/

Amplication Overview

  • **Application**
  • **Environment Variables**
  • **Deployments**
  • **Version Control**
  • **User**
  • **Settings**
  • **Plugins**
  • **Resources**
  • **Roles**
  • **Permissions**
  • **Attributes**
  • **Types**
  • **Services**
  • **Events**
  • **Functions**
  • **Constants**
  • **Enumerations**
  • **Data Sources**
  • **Auth**
  • **Generators**
  • **Logs**
  • **Alerts**
  • **Stats**
  • **GraphQL Documents**
  • **REST Documents**
  • **OpenAPI Documents**
  • **Client Code**
  • **Server Code**
  • **Database Scripts**
  • **Docker Compose**
  • **Terraform Scripts**
  • **Kubernetes Manifests**
  • **Configuration Files**
  • **Code Generation**
  • **Build**
  • **Test**
  • **Deploy**
  • **Monitor**
  • **Scale**
  • **Backup**
  • **Restore**
  • **Upgrade**
  • **Downgrade**
  • **Rollback**
  • **Debug**
  • **Analyze**
  • **Optimize**
  • **Secure**
  • **Compliance**
  • **Governance**
  • **Audit**
  • **Report**
  • **Collaborate**
  • **Integrate**
  • **Extend**
  • **Customize**
  • **Manage**
  • **Configure**
  • **Automate**
  • **Visualize**
  • **Simulate**
  • **Model**
  • **Design**
  • **Develop**
  • **Document**
  • **Generate**
  • **Import**
  • **Export**
  • **Search**
  • **Filter**
  • **Sort**
  • **Paginate**
  • **Group**
  • **Aggregate**
  • **Transform**
  • **Validate**
  • **Verify**
  • **Approve**
  • **Reject**
  • **Comment**
  • **Notify**
  • **Alert**
  • **Remediate**
  • **Resolve**
  • **Escalate**
  • **Assign**
  • **Track**
  • **Measure**
  • **Trend**
  • **Predict**
  • **Forecast**
  • **Plan**
  • **Schedule**
  • **Execute**
  • **Control**
  • **Monitor**
  • **Analyze**
  • **Optimize**
  • **Report**
  • **Alert**
  • **Diagnose**
  • **Repair**
  • **Maintain**
  • **Update**
  • **Patch**
  • **Upgrade**
  • **Downgrade**
  • **Rollback**
  • **Provision**
  • **Deprovision**
  • **Scale**
  • **Backup**
  • **Restore**
  • **Migrate**
  • **Synchronize**
  • **Replicate**
  • **Distribute**
  • **Consolidate**
  • **Isolate**
  • **Segment**
  • **Virtualize**
  • **Containerize**
  • **Orchestrate**
  • **Automate**
  • **Script**
  • **Program**
  • **Code**
  • **Compile**
  • **Build**
  • **Test**
  • **Debug**
  • **Profile**
  • **Analyze**
  • **Optimize**
  • **Secure**
  • **Encrypt**
  • **Decrypt**
  • **Authenticate**
  • **Authorize**
  • **Audit**
  • **Log**
  • **Monitor**
  • **Alert**
  • **Report**
  • **Visualize**
  • **Simulate**
  • **Model**
  • **Design**
  • **Develop**
  • **Document**
  • **Generate**
  • **Import**
  • **Export**
  • **Search**
  • **Filter**
  • **Sort**
  • **Paginate**
  • **Group**
  • **Aggregate**
  • **Transform**
  • **Validate**
  • **Verify**
  • **Approve**
  • **Reject**
  • **Comment**
  • **Notify**
  • **Alert**
  • **Remediate**
  • **Resolve**
  • **Escalate**
  • **Assign**
  • **Track**
  • **Measure**
  • **Trend**
  • **Predict**
  • **Forecast**
  • **Plan**
  • **Schedule**
  • **Execute**
  • **Control**

Use action names and parameters as needed.

Working with Amplication

This skill uses the Membrane CLI to interact with Amplication. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

npm install -g @membranehq/cli@latest

Authentication

membrane login --tenant --clientName=<agentType>

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

membrane login complete <code>

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

Connecting to Amplication

Use `membrane connection ensure` to find or create a connection by app URL or domain:

membrane connection ensure "https://amplication.com/" --json

The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

npx @membranehq/cli connection get <id> --wait --json

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

  • **`READY`** — connection is fully set up. Skip to **Step 2**.
  • **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
  • `clientAction.type` — the kind of action needed:
  • `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
  • `"provide-input"` — more information is needed (e.g. which app to connect to).
  • `clientAction.description` — human-readable explanation of what's needed.
  • `clientActio
Read more
Stats
268
Stars
42
Forks
Maintained
Maintenance
4mo ago
Last commit
6mo ago
Created

Repo: membranedev/application-skills

Other skills on application-skills.