terminaluse
Create, edit, deploy, and interact with agents on TerminalUse. Use when user mentions "tu", "terminaluse", "deploy agent", "create agent", "edit agent", "update agent", "add skills", "agent task", "filesystem", or wants to build/modify/test/run an agent.
What this skill does
# TerminalUse
Build, deploy, interact with agents. Flow: init → deploy → create task → send messages.
Full docs: https://docs.terminaluse.com/llms-full.txt
## Default Rule For New Agents
When creating a new agent, use `tu init` by default.
Only skip `tu init` if the user explicitly instructs another approach (for example, modifying an existing agent template or a pre-scaffolded repository).
## CLI Setup
The `tu` CLI is provided by the `terminaluse` Python package. Before running any `tu` commands:
1. **Verify `tu` is available**:
```bash
which tu || echo "tu CLI not found"
```
2. **If not installed**, ask user whether they would like to install it or if there's a venv they would like to source
3. Ensure you have auth configured:
- Interactive/local: `tu login` then `tu whoami`
- Non-interactive/automation: set `TERMINALUSE_API_KEY` (and optionally `TERMINALUSE_BASE_URL`)
## Context Requirement
Agent-scoped commands often default to `config.yaml` in the current directory when `--agent`/`--config` is omitted.
Before running agent-scoped commands without explicit flags:
```bash
ls config.yaml || echo "Not in agent directory"
```
Use explicit flags when possible:
- `--agent <namespace/name>` to avoid directory coupling
- `--config <path>` when working with a specific manifest
## Quick Reference
| Action | Command |
|--------|---------|
| Login | `tu login`, `tu whoami` |
| Init agent | `tu init` (creates agent directory, no need to mkdir first) |
| Deploy | `tu deploy -y` |
| List deployments | `tu ls` |
| Rollback | `tu rollback` |
| List filesystems | `tu fs ls` |
| List projects | `tu projects ls` |
| Add env var | `tu env add <KEY> -v <val> -e prod\|preview\|all [--secret]` |
| Import env file | `tu env import <file> -e <env> [--secret KEY]` |
| Create task | `tu tasks create --filesystem-id <fs-id> -m "message" [--json]` |
| Create task (auto-create fs) | `tu tasks create -p <project-id> -m "message" [--json]` |
| Send message | `tu tasks send <task-id> -m "message" [--json]` |
| List tasks | `tu tasks ls [--json]` |
| Get task details | `tu tasks get <task-id>` |
`tu fs` is the canonical filesystems command. `tu filesystems` is a supported alias.
`tu tasks ls <id>` is deprecated for single-task retrieval; use `tu tasks get <id>`.
Prefer `--json` for CI/automation and agent-to-agent interaction.
## Workflows
| Task | Reference |
|------|-----------|
| Create or edit an agent | [./workflows/create.md](./workflows/create.md) |
| Deploy to platform | [./workflows/deploy.md](./workflows/deploy.md) |
| Test/interact with agent | [./workflows/interact.md](./workflows/interact.md) |
You must look at the corresponding workflow files based on user intent.
## Anti-patterns
- Creating task without filesystem or project. Tasks either need a filesystem. If project is provided, a filesystem is auto-created in the project
- Modifying Dockerfile `ENTRYPOINT`/`CMD` → breaks deployment
- Trying to use the agent right after updating secrets. You must wait for the new version to become active. Check with `tu ls`
## Error Recovery
| Error | Action |
|-------|--------|
| Deploy fails | `tu ls <branch>` lists deployments events for branch → find FAILED → fix → redeploy |
| Need rollback | `tu rollback` |
## Docs/Skills Feedback
If docs or skills are wrong/unclear, ask user permission to send feedback to (include the feedback in the user request):
Never include any sensitive information.
```bash
curl -X POST 'https://uutzjuuimuclittwbvef.supabase.co/functions/v1/tu-docs-feedback' \
-H 'Content-Type: application/json' \
-d '{"feedback":"<issue>", "page":"<page URL> or section name"}'
```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.