Agent skill

Document Gen Resilient Workflow

by HKUDS in HKUDS/OpenSpace

Robust document generation with engine fallback chain, error diagnostics, and Python alternatives

MITAuto-check passedDocuments & Office

Install Document Gen Resilient Workflow

skills CLI
$ npx skills add HKUDS/OpenSpace --skill document-gen-resilient-workflow -a claude-code

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

GitHub CLI
$ gh skill install HKUDS/OpenSpace document-gen-resilient-workflow --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/document-gen-fallback-enhanced-enhanced .claude/skills/document-gen-resilient-workflow && 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
document-gen-resilient-workflow
GitHub stars
7.8k
Token cost
~3.4k tokens
SKILL.md length
820 words
Files
3
Skills in repo
199
Repo updated
First seen
Licence
MIT

At a glance

Robust document generation with engine fallback chain, error diagnostics, and Python alternatives

  • Works in 5 steps: Validate Workspace → Create Source Content with write_file → Unicode Sanitization (PDF Only) → …
  • Documents & Office work in your project
  • SKILL.md covers When to Use, Core Technique, ⚠️ Critical: Tool Error Patterns and Pre-Flight Checklist, plus 10 more sections
  • Runs Shell scripts from its folder; calls pandoc and apt-get

What it does

Document Gen Resilient Workflow is an agent skill from HKUDS/OpenSpace. Robust document generation with engine fallback chain, error diagnostics, and Python alternatives

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `sanitize_for_pdf.sh`).

It sits in Documents & Office. It works with Python and LaTeX. The repository describes itself as: "OpenSpace: The Skill Management Layer for AI Agents" -- https://open-space.cloud/. The licence is MIT.

When your agent uses it

  • Documents & Office work in your project

Example prompts

  • “/document-gen-resilient-workflow”

Requirements

  • Python 3
  • A Bash shell

Workflow steps

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

  1. Validate Workspace
  2. Create Source Content with write_file
  3. Unicode Sanitization (PDF Only)
  4. Progressive Format Conversion
  5. Verify Output Files

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

    Ships script files (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • pandoc
    • apt-get

    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

Document Gen Resilient Workflow loads about 3.4k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 820 words of instructions outside code blocks.

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

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). 820 words, ~3,353 tokens.

Download SKILL.mdSave it as .claude/skills/document-gen-resilient-workflow/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
document-gen-resilient-workflow
description
Robust document generation with engine fallback chain, error diagnostics, and Python alternatives

Resilient Document Generation Workflow

When to Use

Use this skill when document generation tasks encounter tool errors or failures, especially:

  • run_shell commands return 'unknown error' without diagnostic details
  • PDF generation fails with LaTeX encoding or missing engine errors
  • You need fallback options when primary conversion methods fail
  • Workspace or path issues cause file access problems
  • Unicode/special characters cause rendering issues in PDF output
  • shell_agent has failed multiple times on similar tasks

Core Technique

Split document generation into observable, verifiable steps with explicit error capture and progressive fallback:

  1. Validate workspace → Confirm current directory and write permissions
  2. Pre-flight checks → Verify required tools (pandoc, LaTeX engines) are available
  3. Content creation → Use write_file for source Markdown with full visibility
  4. Unicode sanitization → Preprocess for PDF conversion when needed
  5. Progressive conversion → Try multiple engines/methods until one succeeds
  6. Explicit error capture → Redirect stderr to diagnose failures
  7. Verification → Confirm output files exist and are readable

⚠️ Critical: Tool Error Patterns

'unknown error' from run_shell: This typically indicates:

  • Sandbox execution context issues (not the command itself)
  • Missing stderr capture preventing diagnosis
  • Transient file access problems

Solution: Use explicit error capture with 2>&1 and verify tool availability first:

run_shell
command: pandoc --version 2>&1 || echo "PANDOC NOT AVAILABLE"

Pre-Flight Checklist

Before starting conversion, verify your environment:

markdown
## Pre-Flight Checks

### Check 1: Verify working directory
run_shell
command: pwd && ls -la

### Check 2: Verify pandoc availability
run_shell
command: pandoc --version 2>&1 | head -3 || echo "PANDOC MISSING"

### Check 3: Check LaTeX engines
run_shell
command: which pdflatex xelatex wkhtmltopdf 2>&1 || echo "Some engines missing"

### Check 4: Check Python libraries (fallback option)
run_shell
command: python3 -c "import fpdf; print('fpdf OK')" 2>&1 || echo "fpdf missing"
run_shell
command: python3 -c "import docx; print('python-docx OK')" 2>&1 || echo "python-docx missing"

Complete Step-by-Step Workflow

Step 1: Validate Workspace

Confirm you're in the correct directory and can write files:

run_shell
command: pwd && echo "Test write" > /tmp/workspace_test_$$.txt && ls -la /tmp/workspace_test_$$.txt && rm /tmp/workspace_test_$$.txt

If this fails, you may have directory permission issues. Use absolute paths for all files.

Step 2: Create Source Content with write_file

Write document content as Markdown to a source file:

write_file
path: /tmp/document_source.md
content: |
  # Document Title
  
  ## Section 1
  Content here...
Step 3: Unicode Sanitization (PDF Only)

Only needed for PDF conversion via LaTeX engines. DOCX and HTML handle Unicode natively.

Create a sanitized version replacing LaTeX-problematic characters:

write_file
path: /tmp/document_source_sanitized.md
content: |
  # Document Title
  
  [Same content with: em-dash → --, curly quotes → straight, → arrows → text, etc.]

Common replacements (see full table below):

OriginalReplace With
— (em dash)--
" " (curly quotes)" " (straight)
… (ellipsis)...
→ ← (arrows)-> <-
✓ ✗[x] [ ]
© ® ™(c) (r) (tm)

Alternative: Use sanitization script (see Scripts section below).

Step 4: Progressive Format Conversion

Try multiple methods in order of preference. Capture stderr explicitly for diagnosis.

Method A: DOCX Conversion (Most Reliable)
run_shell
command: pandoc /tmp/document_source.md -o output.docx 2>&1 && echo "SUCCESS" || echo "FAILED: $?"

If this fails, try with explicit UTF-8 flag:

run_shell
command: pandoc /tmp/document_source.md -f markdown+utf8 -o output.docx 2>&1
Method B: PDF Conversion (Progressive Fallback)

Try engines in this order until one succeeds:

run_shell
command: pandoc /tmp/document_source_sanitized.md -o output.pdf 2>&1 | tee /tmp/pdf_error.log && echo "PDF SUCCESS"

If Method B fails, check error log and try next engine:

run_shell
command: pandoc /tmp/document_source_sanitized.md --pdf-engine=xelatex -o output.pdf 2>&1 | tee /tmp/pdf_error.log && echo "PDF SUCCESS"

If xelatex fails:

run_shell
command: pandoc /tmp/document_source_sanitized.md --pdf-engine=wkhtmltopdf -o output.pdf 2>&1 | tee /tmp/pdf_error.log && echo "PDF SUCCESS"
Method C: Python Library Fallback (When pandoc Unavailable)

If all pandoc methods fail, use Python libraries:

Option C1: FPDF2 for PDF

execute_code_sandbox
language: python
code: |
  from fpdf import FPDF
  
  pdf = FPDF()
  pdf.add_page()
  pdf.set_font('Arial', 'B', 16)
  pdf.cell(40, 10, 'Document Title')
  pdf.ln(20)
  pdf.set_font('Arial', '', 12)
  pdf.multi_cell(0, 10, 'Your content here...')
  pdf.output('output.pdf')
  print('PDF created successfully')

Option C2: python-docx for DOCX

execute_code_sandbox
language: python
code: |
  from docx import Document
  
  doc = Document()
  doc.add_heading('Document Title', 0)
  doc.add_paragraph('Your content here...')
  doc.save('output.docx')
  print('DOCX created successfully')
Step 5: Verify Output Files

Don't just check existence—verify files are valid:

run_shell
command: ls -lh output.* 2>&1
run_shell
command: file output.docx output.pdf 2>&1

For DOCX, verify content:

run_shell
command: unzip -p output.docx word/document.xml 2>&1 | head -50 || echo "Cannot read DOCX"

For PDF, check page count:

run_shell
command: pdfinfo output.pdf 2>&1 | grep Pages || echo "pdfinfo not available"

Alternative verification via Python:

execute_code_sandbox
code: |
  import os
  for f in ['output.docx', 'output.pdf', 'output.html']:
    if os.path.exists(f):
      size = os.path.getsize(f)
      print(f'{f}: {size} bytes')
    else:
      print(f'{f}: NOT FOUND')

Complete Example: Generating a Report

markdown
# Generate Quarterly Report (DOCX + PDF)

## Step 1: Pre-flight checks
run_shell
command: pandoc --version 2>&1 | head -1

## Step 2: Write Markdown source
write_file
path: /tmp/quarterly_report.md
content: |
  # Quarterly Business Report
  
  ## Executive Summary
  Q4 performance exceeded expectations...
  
  ## Key Metrics
  - Revenue: $1.2M
  - Growth: 15%
  
  ## Recommendations
  Continue current strategy...

## Step 3: Create sanitized version for PDF
write_file
path: /tmp/quarterly_report_sanitized.md
content: |
  # Quarterly Business Report
  
  ## Executive Summary
  Q4 performance exceeded expectations...
  
  [Rest of content with special chars replaced]

## Step 4: Generate DOCX
run_shell
command: pandoc /tmp/quarterly_report.md -o quarterly_report.docx 2>&1 && echo "DOCX OK"

## Step 5: Generate PDF (try xelatex for Unicode safety)
run_shell
command: pandoc /tmp/quarterly_report_sanitized.md --pdf-engine=xelatex -o quarterly_report.pdf 2>&1 && echo "PDF OK"

## Step 6: Verify outputs
run_shell
command: ls -lh quarterly_report.* && file quarterly_report.*

Full Unicode Replacement Table

CharacterUnicodeIssueSafe Replacement
—U+2014LaTeX incompatible--
–U+2013LaTeX incompatible-
" "U+201C/U+201DEncoding errors" (straight)
' 'U+2018/U+2019Encoding errors' (straight)
…U+2026May not render...
→U+2192LaTeX incompatible-> or to
←U+2190LaTeX incompatible<-
↑ ↓U+2191/U+2193LaTeX incompatible^ v
•U+2022Font-dependent- or *
✓U+2713May not render[x]
✗U+2717May not render[ ]
★ ●U+2605/U+25CFMay not render* -
©U+00A9May require packages(c)
®U+00AEMay require packages(r)
™U+2122May require packages(tm)
é ñ üVariousFont-dependentUse xelatex or replace
Show full SKILL.md (336 more words)Show less

Reusable Sanitization Script

Save this script for repeated use:

bash
#!/bin/bash
# sanitize_for_pdf.sh - Replace problematic unicode chars for LaTeX/PDF
set -e
if [ -z "$1" ]; then
  echo "Usage: $0 <input.md> [output.md]"
  exit 1
fi
INPUT="$1"
OUTPUT="${2:-${1%.md}_sanitized.md}"

sed -e 's/—/--/g' \
    -e 's/–/-/g' \
    -e 's/"\([^"]*\)"/"\1"/g' \
    -e "s/'\([^']*\)'/\'\1\'/g" \
    -e 's/…/.../g' \
    -e 's/→/->/g' \
    -e 's/←/<-/g' \
    -e 's/↑/^/g' \
    -e 's/↓/v/g' \
    -e 's/•/-/g' \
    -e 's/✓/[x]/g' \
    -e 's/✗/[ ]/g' \
    -e 's/★/*/g' \
    -e 's/©/(c)/g' \
    -e 's/®/(r)/g' \
    -e 's/™/(tm)/g' \
    "$INPUT" > "$OUTPUT"

echo "Sanitized: $INPUT -> $OUTPUT"

Usage:

run_shell
command: chmod +x sanitize_for_pdf.sh && ./sanitize_for_pdf.sh /tmp/document_source.md /tmp/document_source_sanitized.md

Error Diagnosis Guide

Error: "unknown error" from run_shell

Diagnosis:

run_shell
command: pandoc --version 2>&1
run_shell
command: echo "test" | pandoc -f markdown -t plain 2>&1

If pandoc works in isolation, the issue is likely:

  • File path problems (use absolute paths)
  • Sandbox context issues (retry or use shell_agent)
  • Transient errors (retry the same command)
Error: "LaTeX not found" or "pdflatex: command not found"

Solutions in order:

  1. Try xelatex: --pdf-engine=xelatex
  2. Try wkhtmltopdf: --pdf-engine=wkhtmltopdf
  3. Install LaTeX: apt-get install texlive-latex-recommended texlive-fonts-recommended
  4. Use Python fpdf2 fallback (see Step 4, Method C)
Error: "Encoding error" or "Invalid UTF-8"

Solutions:

  1. Add UTF-8 flag: pandoc -f markdown+utf8
  2. Check file encoding: file -i source.md
  3. Re-save with explicit UTF-8:
    run_shell
    command: iconv -f UTF-8 -t UTF-8 source.md -o source_utf8.md
  4. Use sanitization step
Error: PDF generated but empty or garbled

Diagnosis:

run_shell
command: pdfinfo output.pdf 2>&1
execute_code_sandbox
code: |
  import fitz  # PyMuPDF
  doc = fitz.open('output.pdf')
  print(f'Pages: {doc.page_count}')
  if doc.page_count > 0:
      page = doc[0]
      print(f'Text: {page.get_text()[:200]}')

Solutions:

  1. Use xelatex engine with Unicode content
  2. Check sanitization step (if using pdflatex)
  3. Verify source markdown is valid
Error: DOCX file won't open or shows error

Diagnosis:

run_shell
command: unzip -l output.docx 2>&1 | head -10

Solutions:

  1. Add --reference-doc with valid template
  2. Ensure markdown syntax is valid
  3. Try pandoc verbose mode: pandoc -v input.md -o output.docx 2>&1

Workspace Troubleshooting

Files appearing in wrong directory

Diagnosis:

run_shell
command: pwd && find /tmp -name "*.docx" -o -name "*.pdf" 2>/dev/null | head -10

Solutions:

  1. Use absolute paths in all commands
  2. Explicitly change to target directory: cd /path/to/workspace && ...
  3. After generation, copy files to correct location:
    run_shell
    command: cp /tmp/output.docx ./output.docx
Permission denied errors

Solutions:

  1. Use /tmp directory for intermediate files
  2. Copy final output to target location
  3. Check disk space: df -h .

When to Use shell_agent vs Manual Workflow

SituationRecommended Approach
Simple DOCX generation, no special charsshell_agent (faster)
PDF with Unicode/symbolsManual workflow with sanitization
Multiple 'unknown error' failuresManual workflow with error capture
Need to debug conversion issuesManual workflow (visible steps)
Time-critical, simple formatshell_agent
Critical document, must succeedManual workflow with fallbacks

Alternative: Hybrid Approach

For reliability with less manual effort:

markdown
## Hybrid Workflow

1. **First attempt**: `shell_agent` with clear task description

2. **On first error**: Switch to manual workflow:
   - `write_file` for source
   - `run_shell` with error capture (2>&1)
   - Verify with explicit checks

3. **On repeated errors**: Use Python library fallback (execute_code_sandbox)

This balances speed with reliability.
  • workspace-path-troubleshooting: For diagnosing file location issues
  • pdf-verification-cli: For validating generated PDFs
  • write-file-fallback-report: For content-first document creation when web sources fail

Quick Reference Card

QUICK START: Generate Document in 3 Formats

1. Write source: write_file → /tmp/doc.md

2. Sanitize (PDF only): 
   Replace: — → --, "" → "", … → ...

3. Convert with error capture:
   DOCX: pandoc /tmp/doc.md -o out.docx 2>&1
   PDF:  pandoc /tmp/doc_sanitized.md --pdf-engine=xelatex -o out.pdf 2>&1
   HTML: pandoc /tmp/doc.md -o out.html 2>&1

4. Verify: ls -lh out.* && file out.*

5. If pandoc fails: Use execute_code_sandbox with fpdf2 or python-docx

© 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 2 other files in benchmarks/gdpval/skills/document-gen-fallback-enhanced-enhanced of HKUDS/OpenSpace.

  • SKILL.md
  • .skill_id
  • sanitize_for_pdf.sh

Open the folder on GitHubat commit 3827781

Compare with similar skills

Document Gen Resilient Workflow 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.

Document Gen Resilient Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Document Gen Resilient Workflow this skillHKUDS/OpenSpace7.8k—~3.4kAutomated safety check: PassMIT
Mathmodel SkillhandsomeZR-netizen/mathmodel-skill292—~2.5kAutomated safety check: PassMIT
Literature Surveyai4s-research/ai4s-skills2372 repos~2kAutomated safety check: PassMIT
My Mathmodel Agentchengyike20110519-create/MathModelRun128—~2.3kAutomated safety check: PassMIT
MineruNebutra/MinerU-Skill122—~504Automated safety check: PassMIT
Cumcm Live Workflowhaoxilin/cumcm-live-workflow-skill181—~3.6kAutomated safety check: PassMIT

Similar skills

  • Mathmodel Skill

    handsomeZR-netizen/mathmodel-skill

    CUMCM 国赛、MCM/ICM 美赛与电工杯数学建模竞赛的端到端协作工作流。Use when a user explicitly works on one of these modeling contests or asks to run/review a modeling-competition paper from problem selection through modeling…

    292 GitHub stars~2.5k tokensUpdated 13 days ago
    Documents & OfficeAuto-check passed
  • Literature Survey

    ai4s-research/ai4s-skills

    A skill your agent uses when the user wants a comprehensive literature survey on a specific research topic.

    237 GitHub starsUsed in 2 repos~2k tokens
    Documents & OfficeAuto-check passed
  • My Mathmodel Agent

    chengyike20110519-create/MathModelRun

    Evidence-driven mathematical modeling contest workflow for CUMCM, MCM/ICM, HiMCM, Huawei Cup, and similar events.

    128 GitHub stars~2.3k tokensUpdated 3 days ago
    Documents & OfficeAuto-check passed
  • Mineru

    Nebutra/MinerU-Skill

    An AI-Native skill for parsing PDF / Office / image files into Markdown with MinerU — a fast, zero-config document parser for AI agents.

    122 GitHub stars~504 tokensUpdated 15 days ago
    Documents & OfficeAuto-check passed
  • Cumcm Live Workflow

    haoxilin/cumcm-live-workflow-skill

    CUMCM(全国大学生数学建模竞赛)真题全流程实战手册。用于完整打一场数模竞赛(环境准备→读题自查→建模出图→LaTeX论文→交叉审阅→填表→AI自查表终审→清理打包),内含题意理解红线、数值严谨性守则、去AIGC特征清单、写作规范、LaTeX编号与图表规范、2026…

    181 GitHub stars~3.6k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • My Mathmodel Agent

    chengyike20110519-create/MathModelRun

    Evidence-driven mathematical modeling contest workflow for Claude Code: decompose a problem, select baseline/primary/fallback model routes, validate PoCs, run reproducible Python/AMPL experiments…

    128 GitHub stars~923 tokensUpdated 3 days ago
    Documents & OfficeAuto-check passed

More from HKUDS/OpenSpace

All 199 skills in this repo
  • 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.8k GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Handle cascading data retrieval tool failures by falling back to embedded knowledge generation

    7.8k GitHub stars~765 tokensUpdated 1 mo ago
    Auto-check passed
  • 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.8k GitHub stars~588 tokensUpdated 1 mo ago
    Auto-check passed
  • 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.8k GitHub stars~652 tokensUpdated 1 mo ago
    Auto-check passed
  • 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.8k GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed
  • Fallback workflow for executing Python code when executecodesandbox fails repeatedly

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

Works with

Questions about Document Gen Resilient Workflow

What does Document Gen Resilient Workflow do?

Robust document generation with engine fallback chain, error diagnostics, and Python alternatives. Document Gen Resilient Workflow is an agent skill from HKUDS/OpenSpace.

When should I use Document Gen Resilient Workflow?

Document Gen Resilient Workflow fits situations like: documents & Office work in your project.

How do I install Document Gen Resilient Workflow in Claude Code?

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

How do I install Document Gen Resilient Workflow in Codex?

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

Can I use Document Gen Resilient Workflow 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 document-gen-resilient-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/document-gen-resilient-workflow, .gemini/skills/document-gen-resilient-workflow, .github/skills/document-gen-resilient-workflow and .opencode/skills/document-gen-resilient-workflow in your project.

What does Document Gen Resilient Workflow need to run?

Going by SKILL.md and its folder, Document Gen Resilient Workflow needs a shell for the scripts in its folder and the command-line tools its instructions call (pandoc and apt-get). Our summary lists: Python 3; A Bash shell.

Does Document Gen Resilient Workflow 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 Document Gen Resilient Workflow 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 Document Gen Resilient Workflow use?

Document Gen Resilient Workflow 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 Document Gen Resilient Workflow use?

About 3.4k tokens (SKILL.md is roughly 13k 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 Document Gen Resilient Workflow?

Skills that share tags, products or a category with Document Gen Resilient Workflow: Mathmodel Skill (handsomeZR-netizen/mathmodel-skill, 292 stars), Literature Survey (ai4s-research/ai4s-skills, 237 stars), My Mathmodel Agent (chengyike20110519-create/MathModelRun, 128 stars) and Mineru (Nebutra/MinerU-Skill, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Document Gen Resilient Workflow?

HKUDS (a GitHub organization) maintains it in HKUDS/OpenSpace, which has 7,750 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.