- Home
- Skills
- Steveclarke
- Dotfiles
- Superthread
superthread_skill
- Shell
31
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill steveclarke/dotfiles --skill superthread- SKILL.md10.4 KB
Overview
This skill provides a command-line interface to manage Superthread project data from your terminal. It streamlines creating and organizing spaces, boards, cards, projects, and related resources so you can run project workflows, queries, and automation scripts without leaving the shell. The CLI is designed for both interactive use and scripting with JSON output and silent options.
How this skill works
The CLI authenticates via an account setup wizard that saves an API key and workspace context. Commands map directly to Superthread concepts (spaces, boards, cards, projects, pages, comments, checklists, tags, sprints) and accept names or IDs. Global flags control account/workspace selection, output format (--json), verbosity, and confirmation behavior for automation.
When to use it
- Create or update cards, boards, spaces, projects and pages from terminal or scripts
- Search workspace content and surface results in scripts or CI with --json
- Assign, tag, link, or relate cards during triage or planning sessions
- Generate automation-friendly output and run non-interactive tasks with -y and --json
- Inspect recent activity or member lists when auditing workspace state
Best practices
- Run suth setup once per machine to store account and workspace context
- Prefer names when working interactively and IDs in scripts to avoid ambiguity
- Use -s SPACE to disambiguate board/list names in shared workspaces
- Use --json for automation and parsing; use -y to skip confirmations in scripted runs
- Use -v for troubleshooting and --quiet in cron/agent runs to minimize noise
Example use cases
- Create a new sprint board and scaffold lists: suth boards create -s SPACE --title "Sprint" then suth boards create-list -b BOARD --title "In Progress"
- Quickly capture a task: suth cards create --title "Fix login bug" -l LIST -b BOARD --priority 1 --owner me
- Find all cards mentioning a keyword across the workspace: suth search query "memory leak" --types card --json
- Automate nightly reporting: suth cards assigned me --since 2026-02-01 --json | jq to generate a digest
- Link cards into an epic or project programmatically: suth projects add_card PROJECT_ID CARD_ID
FAQ
Run suth setup and follow the interactive wizard to add an account, paste your API key, and auto-detect a workspace.
Can I use names instead of IDs?
Yes. Most commands accept names or IDs for spaces, boards, lists, users, and tags; use -s to help resolve ambiguous names.
How do I script safe operations?
Use --json for machine-readable output and -y to skip confirmations. Combine with --verbose for troubleshooting during development.