---
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

| Do | Don't |
|----|-------|
| Pivot quickly after 2+ tool failures | Keep retrying failing tools 5+ times |
| Be transparent about limitations | Claim unverified specifics as facts |
| Provide actionable frameworks | Leave the task incomplete |
| Use professional document structure | Output unstructured text walls |
| Include next-step recommendations | End 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

---
Source attribution: xyliu-cs
Original project: https://github.com/xyliu-cs/OpenSpace-GDPval/blob/af1b40a42167d09c30b3a63000aa14ace4c1e229/gdpval_bench/skills/write-file-fallback-report/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Dave AI.

## Upstream license notice

MIT License

Copyright (c) 2026 ✨Data Intelligence Lab@HKU✨

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Dave AI resource metadata

Creator / publisher: xyliu-cs
Original project: https://github.com/xyliu-cs/OpenSpace-GDPval/blob/af1b40a42167d09c30b3a63000aa14ace4c1e229/gdpval_bench/skills/write-file-fallback-report/SKILL.md
Attribution basis: Source repository record

Fields of work: Content & Media, Marketing, Product Management, Project & Program Management
Roles: Content Marketer, Copywriter, Marketing Analyst, Product Manager, Project Manager
Specialties: Word Documents
Tools: Write_File
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: e24528efde1325f510165d38c6298f3e1f66a28a6011f029a66fb75703d988b2