nsindocs Search the docs⌘K
  1. Docs
  2. API & MCP

Agent Skill

Install one skill and let your AI agent run NSIN and NSIN CLOUD for you — including migrating a domain, site or app from another provider.

On this page

The MCP server gives an agent the tools. The agent skill gives it the judgment.

One file: the CDN, NSIN CLOUD, email routing, and provider migrations. Works with Claude Code, Claude Desktop, Cursor, and any agent that reads skill files.

The short way

Paste this into your agent:

text
I want to use NSIN — the Iranian edge platform (CDN, DNS, SSL, WAF at nsin.ir) and NSIN CLOUD (app hosting at nsincloud.ir). Set yourself up to do that properly, then help me.

**Step 1 — Install the NSIN skill and read it in full.** Try these in order and stop at the first that works:

```
mkdir -p ~/.claude/skills/nsin && curl -fsSL https://nsin.ir/skills/nsin/SKILL.md -o ~/.claude/skills/nsin/SKILL.md
git clone --depth 1 https://github.com/nsincloud/skills /tmp/nsin-skills && cp -r /tmp/nsin-skills/skills/nsin ~/.claude/skills/
```

If you cannot write to that directory, just fetch the file and read it into this conversation. Either way, **read the whole thing before you do anything else** — it has the tool list, the migration procedure and the safety rules you must follow.

**Step 2 — Ask me for what you need.** I have not given you anything yet. Ask me for my NSIN API key, and tell me exactly where to get one. If a task needs credentials for another provider, ask for those separately, tell me the minimum permissions to give them, and let me choose whether to put them in an environment variable, a file, or paste them here. Never ask me for a password.

**Step 3 — Connect.** Add the NSIN MCP servers (`https://api.nsin.ir/mcp` and, if I am hosting apps, `https://api.nsincloud.ir/mcp`), both with `Authorization: Bearer` and my key. Confirm they work by listing my domains before you tell me you are ready.

**Step 4 — Interview me before proposing anything.** Find out:

- What am I trying to do: build something new on NSIN, move something onto it, or fix something that is already there?
- If I am moving: from where? Cloudflare, ArvanCloud, Hamravesh, Coolify, my own VPS, a dedicated server, or something else. And what exactly is moving: DNS, the traffic through the CDN, the application itself, or all three?
- Is there email on any of these domains, and where does it go today?
- Is there a maintenance window, or does this have to be zero-downtime?
- What must not change?

Ask these one topic at a time. Do not dump a questionnaire on me.

**Step 5 — Work this way, always:**

- Read everything first, then show me a written plan with real values in it — every record, rule and app you would create — and wait for me to say yes. Never start applying changes off the back of a conversation.
- Never modify or delete anything at my old provider. Only read from it. I want the old setup intact as my rollback.
- Never change my nameservers or move live traffic on your own. Give me the exact values and let me do it when I am ready.
- Before anything irreversible — deleting an app or a database, purging a cache, replacing MX records — tell me what will be destroyed and whether it comes back, then wait.
- Verify before you tell me it worked, and show me the output you verified against.
- If something needs a plan upgrade or a permission my key does not have, say so plainly instead of working around it.

Start with step 1 now, then ask me your first question.

Persian version.

Installing it yourself

Claude Code, as a plugin

bash
claude plugin marketplace add nsincloud/skills
claude plugin install nsin@nsin

Any agent, one file

bash
mkdir -p ~/.claude/skills/nsin
curl -fsSL https://nsin.ir/skills/nsin/SKILL.md -o ~/.claude/skills/nsin/SKILL.md

Cursor: ~/.cursor/skills/. Other agents, use the installer:

bash
curl -fsSL https://nsin.ir/skills/install.sh -o install.sh
less install.sh
sh install.sh

Then create an API key and connect MCP.

What it knows

  • CDN — domain modes, records, SSL coverage, the fifteen rule kinds, purging, analytics, uptime.
  • NSIN CLOUD — apps from git/zip/image, port detection, databases, custom domains, the catalog, GitOps via an infra repo (nsincloud.yaml schema).
  • Email routing — destinations, verification, MX conflicts.
  • Migration — seven phases; DNS, traffic and app move separately, zone imports before cutover, origin IPs get recovered, curl --resolve verifies before any switch.

What it will not do

  • Touch your old provider — rollback stays intact.
  • Move nameservers or live traffic without you.
  • Ask for a password.
  • Delete an app, database, or MX record without your yes.

API keys can't reach billing, account, or admin endpoints — enforced by the API.

esc