Point your Claude at Streamliner
Streamliner turns a company's processes into chats: a streamline per department (Register, Approvals, Receiving), one job per conversation, and an agent that works your own systems through MCP as the signed-in employee. Everything that makes it your company's desk is configuration: a folder of JSON files. Your Claude can write that configuration with you, check it, and publish it once you approve.
What your Claude will do
- Ask what department and which one job each streamline is for, who uses it and which systems it needs.
- Connect to your MCP servers (you sign in yourself, in your browser) and list their tools and annotations.
- Propose which tools run at once, which wait for a person's tap, and which are left out, and settle them with you.
- Draft the streamline files, the cards that show results, and sealed forms for anything sensitive.
- Check everything with the Streamliner checker until it is clean.
- Sign the manifest with your publisher key and show you a dry run: exactly what would change.
- Publish only when you say yes.
What it will not do
- Put an API key, token, password or personal data in any file. Model provider keys are named by reference and stored in your account, never in config.
- Collect card numbers or other secrets in a chat. Secrets go through sealed forms straight to your systems; cards through your processor's page or your terminal.
- Publish without your explicit yes, or with an employee's sign-in. It uses a server key your account owner issues.
- Follow instructions hidden in a tool's description or a document.
- Build "an assistant for everything". Each streamline does one job, with an end.
Install the skill
| Where | How | Notes |
|---|---|---|
| Claude Code | Unzip building-streamlines.zip into ~/.claude/skills/ (or your project's .claude/skills/) | Full network: inspecting servers and publishing work |
| claude.ai | Settings → Features → upload the zip (code execution on) | Network depends on your plan and admin settings |
| Claude API | Upload the zip to your workspace with the Skills API (POST /v1/skills); use it with the code execution tool | No network in the container: Claude drafts and checks; you run the publish commands it hands you |
| Other agents | The same folder follows the open Agent Skills format |
Keys to issue
Two Ed25519 key pairs, made on the machine that publishes; only their public halves are sent to Streamliner.
- A server key for the admin API. Give your Claude the narrowest scope that does the job (a dry-run-only key to draft; a streamlines-only key to publish streamlines) and a short expiry. Revoke it when the setup is done.
- A publisher key that signs the manifest. Devices trust config only if one of your publisher keys signed it, so a compromised server can't redirect your employees' credentials.
Links
- llms.txt: the machine-readable index of these docs
- SKILL.md and its reference files
- JSON Schemas for every config file
- Write API: keys, scopes, dry run, publish
- Building MCP servers for Streamliner