team-db
Shared team coordination database CLI. Use team-db to read/write the shared task board when working on a team.
Install / Use
npx skills add guitriloco/vivos --skill team-dbInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Data & AnalyticsSupported Platforms
Our assessment of team-db
team-db scores 63/100 on our quality scale, 561st of 598 Data & Analytics skills we index.
Its SKILL.md is 2.8 KB long, well organised into 11 sections with 6 code examples: a solid amount of guidance for an agent.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-11-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
team-db compared with similar skills
All 4 of these similar skills score higher than team-db; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| team-db (this skill)by guitriloco | 63 | 0 | — | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 2mo ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install team-db?
- Run
npx skills add guitriloco/vivos --skill team-db. The install tabs above show the steps for each supported agent. - Which AI agents does team-db work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is team-db safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is team-db still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubname: team-db description: Shared team coordination database CLI. Use team-db to read/write the shared task board when working on a team. allowed-tools:
- bash
team-db — Shared Team Database CLI
team-db is the only way to access the shared team coordination database. It connects to a local SQLite database synced with Turso, ensuring all team members see the same data.
NEVER use sqlite3 or write to the .db file directly — only team-db triggers sync with Turso.
Usage
team-db <sql> # Pull, execute, push. Always prints JSON (rows for queries, [] for mutations).
team-db --help # Show usage
Every invocation automatically: pulls latest from Turso, executes your SQL, pushes changes back.
Database Schema
| Table | Purpose |
| -------- | --------------------------------------------------------- |
| config | Team configuration (read-only) |
| agents | Team member roster |
| tasks | Kanban task board (backlog → in-progress → review → done) |
Tasks columns
| Column | Description |
| ------------- | ----------------------------------------------- |
| id | Unique task identifier |
| title | Short task title |
| description | What needs to be done |
| status | backlog, in-progress, review, or done |
| created_by | Who created the task |
| assigned_to | Who is working on it (NULL if unassigned) |
| result | Summary of completed work (set when completing) |
Common Patterns
Check tasks assigned to you
team-db "SELECT id, title, description FROM tasks WHERE assigned_to = '<your-id>' AND status = 'in-progress'"
Mark a task in progress
team-db "UPDATE tasks SET status = 'in-progress', updated_at = datetime('now') WHERE id = '<task-id>'"
Complete a task with result
Always write a result — this is how teammates see your output:
team-db "UPDATE tasks SET status = 'done', result = '<summary of work and findings>', updated_at = datetime('now') WHERE id = '<task-id>'"
Read teammates' completed work
team-db "SELECT id, title, assigned_to, result FROM tasks WHERE status = 'done'"
Check the full board
team-db "SELECT id, title, status, assigned_to FROM tasks ORDER BY created_at"
Important
- Every
team-dbcall syncs automatically (pull → execute → push). - Always write a result when completing a task. This is the only way teammates can see your work.
- Task assignment is managed by the team lead. Members should not reassign tasks.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
