Skip to content
Back to skills

Cocofleet

ASecurity

Show output logs for a specific CocoFleet instance. If the instance is still running, tails the live log. If complete, shows the full log with status summary. Usage: $fleet logs [fleet-id] [instance-id].

  • 724 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agentsnode

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add Snowflake-Labs/cocoplus --skill cocofleet --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cocofleet?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cocofleet
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/snowflake-labs-cocofleet-81b1a838/badge)](https://www.skillsdirectory.com/skills/snowflake-labs-cocofleet-81b1a838)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "fleet-logs"
description: "Show output logs for a specific CocoFleet instance. If the instance is still running, tails the live log. If complete, shows the full log with status summary. Usage: $fleet logs [fleet-id] [instance-id]."
version: "1.0.0"
author: "CocoPlus"
tags:
  - cocoplus
  - cocofleet
---

Your objective is to show output logs for a CocoFleet instance.

Before proceeding, verify that `.cocoplus/` exists.
If not: output "CocoPlus not initialized in this directory. Run `$pod init` to begin." Then stop.

Parse arguments: `$fleet logs [fleet-id] [instance-id]`
If missing: output "Usage: $fleet logs [fleet-id] [instance-id]" Then stop.

Log file: `.cocoplus/fleet/[instance-id]/output.log`
If not found: output "No log file found for [instance-id]. The instance may not have started yet." Then stop.

Read state file to determine if instance is still running.
Check if PID in state.json is alive using a cross-platform Node.js one-liner:
`node -e "try{process.kill([pid],0);console.log('alive')}catch(e){console.log('dead')}"`

If alive (instance still running):
- Output last 50 lines of output.log
- Append: "[Instance is still running — showing last 50 lines. Re-run `$fleet logs` to refresh.]"

If dead (instance complete or stopped):
- Output full log content
- Append status summary from state.json (completed/failed, checkpoints satisfied)

## Anti-Rationalization

| Shortcut / Temptation | Why It Fails |
|-----------------------|--------------|
| Always show full log regardless of whether instance is running | For running instances, full log output may be many thousands of lines — tail 50 is the correct live view |
| Show logs without checking instance status first | Showing "complete" status for a still-running instance misleads the developer into thinking work is done |

## Exit Criteria

- [ ] Log content from `.cocoplus/fleet/[instance-id]/output.log` is displayed
- [ ] If instance is running: only last 50 lines shown with a "[still running]" notice
- [ ] If instance is complete: full log shown with status summary from state.json (checkpoints satisfied or not)

Files in this skill

  • fleet-comms.skill.md1.8 KB
  • fleet-init.skill.md3.8 KB
  • fleet-logs.skill.md2.1 KB
  • fleet-run.skill.md6.2 KB
  • fleet-status.skill.md2.7 KB
  • fleet-stop.skill.md2.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…