New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Write File Fallback Report

by HKUDS in HKUDS/OpenSpace

Generate professional documents using writefile when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval

MITAuto-check passed

Install Write File Fallback Report

skills CLI
$ npx skills add HKUDS/OpenSpace --skill write-file-fallback-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HKUDS/OpenSpace write-file-fallback-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HKUDS/OpenSpace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/gdpval/skills/write-file-fallback-report .claude/skills/write-file-fallback-report && rm -rf skills-src

Use ~/.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/

Facts

Skill name
write-file-fallback-report
GitHub stars
7.7k
Token cost
~1.2k tokens
SKILL.md length
325 words
Files
2
Skills in repo
199
Repo updated
First seen
Licence
MIT

At a glance

Generate professional documents using writefile when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval

  • Works in 5 steps: Detect Tool Failure Pattern → Pivot to Write-File-First Approach → Structure the Document Professionally → …
  • SKILL.md covers When to Use This Skill, Step-by-Step Instructions, Code Example and Best Practices, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Write File Fallback Report is an agent skill from HKUDS/OpenSpace. Generate professional documents using writefile when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.

The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.

Example prompts

  • “/write-file-fallback-report”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Detect Tool Failure Pattern
  2. Pivot to Write-File-First Approach
  3. Structure the Document Professionally
  4. Leverage Embedded Domain Knowledge
  5. Execute and Validate

What it can do on your machine

Read from SKILL.md and the folder at commit 3827781. 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 (its code samples are markdown and python).

    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

Write File Fallback Report loads about 1.2k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 325 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

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

The full file from HKUDS/OpenSpace at commit 3827781, republished under its MIT licence (© HKUDS). 325 words, ~1,152 tokens.

Download SKILL.mdSave it as .claude/skills/write-file-fallback-report/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
write-file-fallback-report
description
Generate professional documents using write_file when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval

Write-File Fallback Report Generation

When to Use This Skill

Use this workflow when attempting to generate a document or report, but multiple primary data source tools fail simultaneously:

  • read_file returns binary/image data instead of text (common with PDFs)
  • search_web returns errors or no results
  • execute_code_sandbox fails unexpectedly
  • Other data retrieval tools are unavailable

Key insight: Rather than getting stuck on failed data retrieval, pivot immediately to generating the document directly with write_file using professionally structured content and embedded domain knowledge.

Step-by-Step Instructions

Step 1: Detect Tool Failure Pattern

Recognize when you're in a fallback scenario:

TOOL_FAILURE_INDICATORS = [
    "read_file returns binary or image data",
    "search_web returns unknown error or empty results",
    "execute_code_sandbox fails repeatedly",
    "Multiple consecutive tool failures on data retrieval"
]

Decision point: If 2+ indicators are present, proceed to Step 2.

Step 2: Pivot to Write-File-First Approach

Stop attempting to fix the failing tools. Instead:

  1. Acknowledge the limitation briefly in your output
  2. Commit to generating the document with available knowledge
  3. Use write_file as your primary tool (not a last resort)
Step 3: Structure the Document Professionally

Create a well-organized markdown document with:

markdown
# [Document Title]

## Executive Summary
[Brief overview of key findings/content]

## Background
[Context and scope - use embedded knowledge]

## Main Content
[Organized sections with headers, lists, tables as appropriate]

## Limitations & Notes
[Transparent about data source limitations if relevant]

## Recommendations/Next Steps
[Actionable guidance based on available information]
Step 4: Leverage Embedded Domain Knowledge

When external data is unavailable:

  • Use general domain knowledge appropriately
  • Clearly distinguish between verified facts and general guidance
  • Include actionable frameworks rather than specific unverified data
  • Add placeholder notes where specific data would enhance the document

Example:

markdown
> **Note**: Specific [metric/data point] would typically be sourced from 
> [expected source]. The guidance below reflects established best practices 
> in this domain.
Step 5: Execute and Validate
python
# Example execution pattern
write_file(
    path="output/report.md",
    content=professionally_structured_markdown
)
# Verify the file was created successfully
list_dir(path=".")  # Confirm file exists

Code Example

python
# Detection and pivot pattern
def detect_and_pivot(task_goal):
    # After detecting tool failures:
    
    report_content = f"""# {task_goal} Report

## Executive Summary
This report was generated using established domain knowledge due to 
temporary unavailability of primary data sources.

## Key Frameworks and Guidance
[Structured content with headers, bullets, tables]

## Limitations
- Specific data points from [expected sources] were unavailable
- Recommendations based on general best practices

## Action Items
1. [Concrete step 1]
2. [Concrete step 2]
"""
    
    write_file(path="generated_report.md", content=report_content)
    return "Report generated successfully with embedded knowledge"

Best Practices

DoDon't
Pivot quickly after 2+ tool failuresKeep retrying failing tools 5+ times
Be transparent about limitationsClaim unverified specifics as facts
Provide actionable frameworksLeave the task incomplete
Use professional document structureOutput unstructured text walls
Include next-step recommendationsEnd without clear guidance

Common Pitfalls

  1. Over-apologizing: Acknowledge limitations once, then deliver value
  2. Under-delivering: A well-structured partial report beats no report
  3. Misrepresenting certainty: Use appropriate hedging language
  4. Skipping structure: Professional formatting increases usability

Success Criteria

The skill is successfully applied when:

  • Document is generated despite tool failures
  • Content is professionally structured (headers, sections, lists)
  • Limitations are transparently noted
  • Actionable guidance is provided
  • File is successfully created and verified

© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in benchmarks/gdpval/skills/write-file-fallback-report of HKUDS/OpenSpace.

  • SKILL.md
  • .skill_id

Open the folder on GitHubat commit 3827781

Compare with similar skills

Write File Fallback Report 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.

Write File Fallback Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Write File Fallback Report this skillHKUDS/OpenSpace7.7k—~1.2kAutomated safety check: PassMIT
Offline Fallbackthedaviddias/Front-End-Checklist74k—~488Automated safety check: PassMIT
Openrouter Fallback Configjeremylongshore/tons-of-skills-marketplace2.8k—~2.4kAutomated safety check: PassMIT
Customerio Primary Workflowjeremylongshore/tons-of-skills-marketplace2.8k—~2.3kAutomated safety check: PassMIT
PDF Extraction FallbacksHKUDS/OpenSpace7.7k—~1.8kAutomated safety check: PassMIT
Execute Code FallbackHKUDS/OpenSpace7.7k—~1kAutomated safety check: PassMIT

Similar skills

  • Offline Fallback

    thedaviddias/Front-End-Checklist

    A skill your agent uses when adding PWA capabilities, implementing a service worker, or improving the experience for users on unreliable network connections.

    74k GitHub stars~488 tokensUpdated 2 days ago
    Auto-check passed

  • Openrouter Fallback Config

    jeremylongshore/tons-of-skills-marketplace

    Configure automatic model fallbacks for high availability on OpenRouter.

    2.8k GitHub stars~2.4k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Customerio Primary Workflow

    jeremylongshore/tons-of-skills-marketplace

    Implement Customer.io primary messaging workflow. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2.3k tokensUpdated today
    Backend & APIsAuto-check passed

  • PDF Extraction Fallbacks

    HKUDS/OpenSpace

    Multi-fallback PDF/text extraction with early failure detection and sequential tool fallbacks

    7.7k GitHub stars~1.8k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

  • Execute Code Fallback

    HKUDS/OpenSpace

    Fallback from executecodesandbox to runshell when e2b sandbox is unavailable

    7.7k GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed

  • Sandbox Fallback Execution

    HKUDS/OpenSpace

    Fallback workflow for executing Python code when executecodesandbox fails

    7.7k GitHub stars~740 tokensUpdated 1 mo ago
    Auto-check passed

More from HKUDS/OpenSpace

All 199 skills in this repo

  • Audio Track Production Workflow

    HKUDS/OpenSpace

    Walks through producing a master audio track plus stems in Python, from checking a reference file and timing sections by BPM to effects, a zip archive and final verification.

    7.7k GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed

  • Cascade Failure Recovery

    HKUDS/OpenSpace

    Handle cascading data retrieval tool failures by falling back to embedded knowledge generation

    7.7k GitHub stars~765 tokensUpdated 1 mo ago
    Auto-check passed

  • Sandbox Code Execution Fallback

    HKUDS/OpenSpace

    Gives an agent a workaround when its code-execution sandbox keeps failing: save the Python script to a file and run it through the shell instead.

    7.7k GitHub stars~588 tokensUpdated 1 mo ago
    Auto-check passed

  • Code Execution Fallback

    HKUDS/OpenSpace

    A recovery routine for agents whose sandboxed code runner keeps failing: save the Python script to disk, then run it through the shell and read the output.

    7.7k GitHub stars~652 tokensUpdated 1 mo ago
    Auto-check passed

  • Code Execution Fallback and Path Anchoring

    HKUDS/OpenSpace

    Fallback ladder for failed sandboxed code runs, plus the habit of fixing the working directory first so generated files land in the right place.

    7.7k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Code Execution Fallback E81068

    HKUDS/OpenSpace

    Fallback workflow for executing Python code when executecodesandbox fails repeatedly

    7.7k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

Questions about Write File Fallback Report

What does Write File Fallback Report do?

Generate professional documents using writefile when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval. Write File Fallback Report is an agent skill from HKUDS/OpenSpace.

How do I install Write File Fallback Report in Claude Code?

Run `npx skills add HKUDS/OpenSpace --skill write-file-fallback-report -a claude-code`. Or copy the skill folder (benchmarks/gdpval/skills/write-file-fallback-report in HKUDS/OpenSpace) into .claude/skills/write-file-fallback-report in your project. Claude Code loads it when a task matches its description.

How do I install Write File Fallback Report in Codex?

Run `npx skills add HKUDS/OpenSpace --skill write-file-fallback-report -a codex`. Or copy the skill folder (benchmarks/gdpval/skills/write-file-fallback-report in HKUDS/OpenSpace) into .agents/skills/write-file-fallback-report in your project. Codex loads it when a task matches its description.

Can I use Write File Fallback Report 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 HKUDS/OpenSpace --skill write-file-fallback-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-file-fallback-report, .gemini/skills/write-file-fallback-report, .github/skills/write-file-fallback-report and .opencode/skills/write-file-fallback-report in your project.

What does Write File Fallback Report need to run?

SKILL.md names no scripts, command-line tools or credentials: Write File Fallback Report is instructions for the agent only. Our summary lists: Python 3.

Does Write File Fallback Report 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 Write File Fallback Report 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 Write File Fallback Report use?

Write File Fallback Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Write File Fallback Report use?

About 1.2k tokens (SKILL.md is roughly 4.6k 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 Write File Fallback Report?

Skills that share tags, products or a category with Write File Fallback Report: Offline Fallback (thedaviddias/Front-End-Checklist, 74k stars), Openrouter Fallback Config (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Customerio Primary Workflow (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and PDF Extraction Fallbacks (HKUDS/OpenSpace, 7.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Write File Fallback Report?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,749 GitHub stars. The repository holds 199 skills in this directory. The repository was last updated on August 12, 2026.

Source: HKUDS/OpenSpace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.