Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
Loads when a workspace job tool returns success: true, status: completed AND (summary: "" OR artifactIds: [] OR summary equals "Session completed without producing a summarizable document").
Install Debugging Empty Output
$ npx skills add friday-platform/friday-studio --skill debugging-empty-output -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install friday-platform/friday-studio debugging-empty-output --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/system/skills/debugging-empty-output .claude/skills/debugging-empty-output && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debugging-empty-output" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-empty-output into .claude/skills/debugging-empty-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-empty-output", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-empty-outputType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add friday-platform/friday-studio --skill debugging-empty-output -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install friday-platform/friday-studio debugging-empty-output --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/system/skills/debugging-empty-output .agents/skills/debugging-empty-output && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-empty-output" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-empty-output into .agents/skills/debugging-empty-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-empty-output", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill debugging-empty-output -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install friday-platform/friday-studio debugging-empty-output --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/system/skills/debugging-empty-output .cursor/skills/debugging-empty-output && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debugging-empty-output" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-empty-output into .cursor/skills/debugging-empty-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-empty-output", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/friday-platform/friday-studio.git --path packages/system/skills/debugging-empty-output--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add friday-platform/friday-studio --skill debugging-empty-output -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install friday-platform/friday-studio debugging-empty-output --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/system/skills/debugging-empty-output .gemini/skills/debugging-empty-output && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debugging-empty-output" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-empty-output into .gemini/skills/debugging-empty-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-empty-output", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install friday-platform/friday-studio debugging-empty-outputInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add friday-platform/friday-studio --skill debugging-empty-output -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/system/skills/debugging-empty-output .github/skills/debugging-empty-output && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debugging-empty-output" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-empty-output into .github/skills/debugging-empty-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-empty-output", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add friday-platform/friday-studio --skill debugging-empty-output -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install friday-platform/friday-studio debugging-empty-output --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/friday-platform/friday-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/system/skills/debugging-empty-output .opencode/skills/debugging-empty-output && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debugging-empty-output" agent skill from https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/debugging-empty-output into .opencode/skills/debugging-empty-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-empty-output", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debugging-empty-output- GitHub stars
- 104
- Token cost
- ~1.1k tokens
- SKILL.md length
- 452 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Loads when a workspace job tool returns success: true, status: completed AND (summary: "" OR artifactIds: [] OR summary equals "Session completed without producing a summarizable document").
- Works in 4 steps: Read aiSummary.summary from… → Inspect agentBlocks[].toolCalls for… → Check the agent prompt's instructions → …
- Tasks that involve Debugging
- SKILL.md covers Diagnostic checklist, What NOT to do and Cross-references
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Debugging Empty Output is an agent skill from friday-platform/friday-studio. Loads when a workspace job tool returns success: true, status: completed AND (summary: "" OR artifactIds: [] OR summary equals "Session completed without producing a summarizable document"). Diagnostic checklist for sessions that ran successfully but emitted nothing useful. Most common cause: the agent's prompt didn't instruct the LLM to call complete() for an outputTo action. Do NOT migrate Pattern A → Pattern B FSM as a fix — that's almost always wrong.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Debugging. The repository describes itself as: Agent Harness Platform — shareable workspaces, MCP tools, skills, memory, and cron/webhook automations. Self-hosted and transparent.
When your agent uses it
- Tasks that involve Debugging
Example prompts
- “OR artifactIds: [] OR summary equals”
- “s prompt didn”
- “Use the debugging-empty-output skill to load when a workspace job tool returns success: true, status: completed AND (summary: "" OR artifactIds: []…”
- “/debugging-empty-output”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Read aiSummary.summary from describe_session
- Inspect agentBlocks[].toolCalls for complete
- Check the agent prompt's instructions
- Confirm via test invocation
What it can do on your machine
Read from SKILL.md and the folder at commit fb3069a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debugging Empty Output loads about 1.1k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 452 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 452 words (~1,080 tokens).
“Symptom: session status: completed but the chat-tool wrapper got back nothing useful — empty summary, empty artifactIds, or the sentinel "Session completed without producing a summarizable document."”
- name
- debugging-empty-output
Files
Just SKILL.md in packages/system/skills/debugging-empty-output of friday-platform/friday-studio.
Open the folder on GitHubat commit fb3069a
Compare with similar skills
Debugging Empty Output next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debugging Empty Output this skillfriday-platform/friday-studio | 104 | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Trellis Session Insightmindfold-ai/Trellis | 15k | 4 repos | ~1.7k | Automated safety check: Pass | AGPL-3.0 | |
| Native Data FetchingCherryHQ/cherry-studio-app | 4k | 6 repos | ~2.9k | Automated safety check: Notes | MIT | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Herdr Throwaway Reproductionherdrdev/herdr | 43k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Systematic Debuggingultralisp/ultralisp | 258 | 51 repos | ~2.4k | Automated safety check: Pass | None |
Similar skills
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
More from friday-platform/friday-studio
All 20 skills in this repoAuthoring Skills
friday-platform/friday-studio
Authors new agent skills that follow the Anthropic + agentskills.io specification.
Friday CLI
friday-platform/friday-studio
Interacts with a running Friday daemon via CLI and HTTP — lists/creates/modifies workspaces, triggers signals, watches sessions, publishes skills and agents.
Workspace API
friday-platform/friday-studio
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL.
Writing Workspace Signals
friday-platform/friday-studio
Authors Friday workspace signals with correct provider configs, payload schemas, and runtime wiring.
Composing Emails
friday-platform/friday-studio
General styling and tone guidelines for composing HTML emails.
Repairing Workspaces Agents
friday-platform/friday-studio
Repairs and upgrades existing Friday workspaces, jobs, user agents, and generated agents to current runtime contracts.
Related
Categories
Questions about Debugging Empty Output
What does Debugging Empty Output do?
Loads when a workspace job tool returns success: true, status: completed AND (summary: "" OR artifactIds: [] OR summary equals "Session completed without producing a summarizable document"). Debugging Empty Output is an agent skill from friday-platform/friday-studio. Loads when a workspace job tool returns success: true, status: completed AND (summary: "" OR artifactIds: [] OR summary equals "Session completed without producing a summarizable document").
When should I use Debugging Empty Output?
Debugging Empty Output fits situations like: tasks that involve Debugging.
How do I install Debugging Empty Output in Claude Code?
Run `npx skills add friday-platform/friday-studio --skill debugging-empty-output -a claude-code`. Or copy the skill folder (packages/system/skills/debugging-empty-output in friday-platform/friday-studio) into .claude/skills/debugging-empty-output in your project. Claude Code loads it when a task matches its description.
How do I install Debugging Empty Output in Codex?
Run `npx skills add friday-platform/friday-studio --skill debugging-empty-output -a codex`. Or copy the skill folder (packages/system/skills/debugging-empty-output in friday-platform/friday-studio) into .agents/skills/debugging-empty-output in your project. Codex loads it when a task matches its description.
Can I use Debugging Empty Output in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add friday-platform/friday-studio --skill debugging-empty-output -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-empty-output, .gemini/skills/debugging-empty-output, .github/skills/debugging-empty-output and .opencode/skills/debugging-empty-output in your project.
What does Debugging Empty Output need to run?
SKILL.md names no scripts, command-line tools or credentials: Debugging Empty Output is instructions for the agent only.
Does Debugging Empty Output access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debugging Empty Output safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Debugging Empty Output use?
Debugging Empty Output has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Debugging Empty Output use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Debugging Empty Output?
Skills that share tags, products or a category with Debugging Empty Output: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Aoti Debug (pytorch/pytorch, 104k stars) and Herdr Throwaway Reproduction (herdrdev/herdr, 43k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debugging Empty Output?
friday-platform (a GitHub organization) maintains it in friday-platform/friday-studio, which has 104 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on September 5, 2026.
Source: friday-platform/friday-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.