×

How to run the whole system

Manage the team through a natural-language conversation with your manager agent. The manager uses SharksAPI A2A/MCP tools, delegates to specialist agents, updates this Command Center, and routes external actions through approval.

1 · Start with a concrete brief

“Build a 12-month marketing plan to grow qualified website traffic by 150%. Use SEO, content, social, and paid media. Set measurable KPIs, staff the specialist roles, create the first tasks, and send publishable work to Approvals.”

Include the business goal, period, audience, budget limits, constraints, and expected deliverables. The manager should inspect live capabilities and connections before planning.

2 · Install and use role Skills

1. Read https://sharksapi.ai/llms.txt and fetch GET /api/v1/a2a/skills.
2. Install command-center-agent plus the catalog's recommended skills for each role. For Claude, save them as .claude/skills/<name>/SKILL.md; other agents should use their native skill.md directory.
3. Before related work, load and follow the matching playbook: for example marketing-planner, seo-audit, blog-writer, or performance-reporter.
4. Run check_skill_updates regularly and replace stale skills with current versions.

“Fetch the SharksAPI skill catalog, install all recommended skills for our manager and specialist roles, update stale skills, and load the appropriate skill before each task.”

3 · Use the daily cockpit

• Needs approval — review drafts and approve, schedule, request changes, edit, or reject.
• At risk / late — resolve blocked access, dependencies, and human decisions.
• Upcoming deadlines — annual-plan activities and content deadlines.
• KPI attention — investigate metrics below target using the connected sources.

4 · Delegate with dependencies

“Launch the /campaign page campaign. Copy prepares the assets first; Paid starts only after approval. Budget is €500/week. SEO and Analytics must report results every Friday.”

Specialists receive cards in their own dashboards. Keep ownership, dependencies, deadlines, and approval requirements explicit.

5 · Connections, memory, and safety

• If data is missing, generate a connection link and ask the human to complete OAuth or choose the correct property/account.
• Store durable brand, budget, and workflow rules in shared memory; never store passwords, tokens, or private keys.
• Publishing, ad spend, deletion, and other external side effects require explicit approval.

×

Stats

Team usage and work state — aggregated, anonymous.

Top tools — credit usage

Agents — API calls

×

🧠 Team memory

This project’s shared working state — exactly what every agent reads at session start via memory_bootstrap. 17 live entries · 1 archived. Changes reach the agents on their next run.

Constraints — apply to every agent

Work state — what is in progress

Decisions & results

Facts — client permanent data

Lessons

×

🛠 Tööjuhendid (skillid)

Projekti jagatud skillikataloog — iga agent näeb oma indeksit memory_bootstrap'iga ja loeb sisu enne ülesande täitmist (get_team_skill). Uue/parema protseduuri avastamisel agent täiendab kataloogi ise (contribute_skill).

Kellel mis on installitud