القائمة
Use this skill to monitor a long-running Sokosumi task or job from a headless coding-agent environment and report back automatically when it finishes, fails, or needs user input.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use this skill to route onboarding, agent selection, open-work review, workflow coordination, and general Sokosumi operations to Elena or the closest available Sokosumi coworker/agent. Prefer the headless Sokosumi CLI with --json and an API key.
Typo alias for the Sokosumi research skill. Use when the user types /reseach or otherwise misspells research while asking for a Sokosumi research workflow.
Use this skill to browse, search, inspect, and hire Sokosumi marketplace agents from a headless coding-agent environment using the Sokosumi CLI and API key.
Use this skill to route marketing, growth, competitor, SEO, AI visibility, audience, positioning, campaign, or market-research work to Hannah or the closest available Sokosumi coworker/agent from a headless coding-agent environment. Prefer the Sokosumi CLI with --json and an API key; do not launch the Ink TUI.
Use this skill to check Sokosumi jobs, statuses, outputs, and follow-up actions from a headless coding-agent environment using the Sokosumi CLI.
Use this skill for Sokosumi market and marketing workflows: campaign strategy, positioning, competitors, audience research, SEO, AI visibility, and market analysis. Prefer Hannah unless the user explicitly asks for a direct specialist agent.
| name | watch |
| description | Use this skill to monitor a long-running Sokosumi task or job from a headless coding-agent environment and report back automatically when it finishes, fails, or needs user input. |
| metadata | {"internal":false} |
Use this skill after creating a READY coworker task or a direct agent job that is still running. The goal is that the human does not need to manually ask whether the work is done.
Use SOKOSUMI_API_KEY if set. Otherwise ask the user to create one at https://app.sokosumi.com/connections.
sokosumi tasks get task_or_job_id --api-key "$SOKOSUMI_API_KEY" --json
sokosumi jobs get task_or_job_id --details --api-key "$SOKOSUMI_API_KEY" --json
$SOKOSUMI_API_KEY; never paste the key value into the command or a file.For a task, run a background shell command equivalent to:
for i in $(seq 1 60); do
status=$(sokosumi tasks get <ID> --api-key "$SOKOSUMI_API_KEY" --json | node -e 'let s="";process.stdin.on("data",d=>s+=d);process.stdin.on("end",()=>{let j=JSON.parse(s||"{}");console.log(j.task?.status||"")})')
case "$status" in
COMPLETED|FAILED|CANCELED|CANCELLED|AUTHENTICATION_REQUIRED) echo "SOKOSUMI-WATCH-DONE task <ID> $status"; exit 0;;
esac
sleep 60
done
echo "SOKOSUMI-WATCH-TIMEOUT task <ID>"
For a job, use sokosumi jobs get <ID> --details --json and treat completed or failed as terminal.
SOKOSUMI-WATCH-DONE: fetch final details once with sokosumi tasks get <ID> --api-key "$SOKOSUMI_API_KEY" --json or sokosumi jobs get <ID> --details --api-key "$SOKOSUMI_API_KEY" --json, then summarize status, output, files, links, and any requested user action.SOKOSUMI-WATCH-TIMEOUT: tell the user the work is still running after about 60 minutes and offer to keep watching.Do not run two monitors for the same id.