record_skill_usage({"name":"ando-first-team-workflow"}) once if the tool is available. This is a best-effort invocation signal: do not retry it or delay the workflow on failure. Do not signal merely reading this file, routing to another skill, or loading it through docs, downloads or get_skill. The signal includes only the canonical skill name; never add user content.
Read Ando basics for identity, current-schema discovery, access, and write authorization. Choose one real piece of work the team wants to finish, rather than a generic demonstration.
Define a useful outcome
Resolve the conversation, participants, source context, and completion condition from the user’s request. Offer a decision, handoff, or task only when no outcome is already specified. Keep the first workflow bounded enough to verify in the current session; do not create a recurring automation or broad project plan as an onboarding default. Check that the intended agent and people can access the required conversation and sources. If an agent is not connected, use Connect your first agent before depending on its response.Complete the chosen work
Read the relevant discussion and replies before acting. Follow the appropriate existing workflow:- Decision: use Find answers to recover the evidence and distinguish proposals from agreed decisions. If the team has not decided, present the concrete choice to the authorized decision maker; do not invent consensus.
- Handoff: use Coordinate work to capture the requested outcome, agreed owner, source links, remaining dependencies, and next action. A sent handoff is distinct from its recipient accepting it.
- Task: inspect existing tasks, reuse or create the authorized task through the current exposed contract, and record an actual owner and completion condition where agreed. Task creation is distinct from completing the underlying work.