Skip to content
cccskills
FreePublished on GitHub

prioritize-context-data

Use attached spreadsheets and documents as the primary source for reports and analysis. Identify relevant files, extract needed data, and cite filenames, turning to external searches or clearly labeled estimates only when the supplied material lacks required information.

OriginalShow the original description

Ensures agents check and use provided context files for data before attempting external searches.

Works withExcel
See how to install

Good for

  • Preparing a report from an attached Excel file
  • Extracting required figures from CSV or PDF files
  • Citing the source filename for reported data
  • Separating file data from external findings and estimates

Files included (2)

  • SKILL.md3.2 KB
  • .skill_id37 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Prioritize Context Data

Objective

Prevent data hallucination and inefficiency by mandating that agents inspect and utilize provided reference files (CSV, XLSX, PDF, TXT, etc.) before attempting web searches or generating synthetic data.

Critical Rule

If a reference file is provided in the task context, it is the source of truth. Do not fabricate data or search the web for information that exists within the provided attachments.

Workflow Steps

1. Scan Context for Attachments

At the start of every task, explicitly list all files provided in the context window or attachment panel.

  • Check for spreadsheets (.xlsx, .csv), documents (.pdf, .docx), or data dumps (.json, .txt).
  • Note the filename and inferred content type.

2. Evaluate Relevance

Determine if any provided file contains the data required to complete the task.

  • Match Keywords: Do filenames or column headers match task requirements?
  • Check Scope: Does the data cover the necessary timeframe or地域 (region)?

3. Extract Data First

If relevant files are found:

  • Read the file content using appropriate tools (e.g., read_file, pandas, pdf_reader).
  • Extract the specific data points needed.
  • Do not proceed to web search until you have confirmed the file lacks the necessary information.

4. Cite Source Explicitly

When presenting data in the final output:

  • Explicitly state which file the data came from.
  • Example: "According to Massabama_active_listings.xlsx..."
  • This verifies to the user that real data was used, not hallucinated.

5. Fallback to Search (Only if Necessary)

If the provided files do not contain the specific data needed:

  • State clearly what was missing from the files.
  • Then proceed with web search or estimation.
  • Mark any non-file data as "External Search" or "Estimated".

Checklist

  • Did I list all attached files?
  • Did I open and read the relevant files?
  • Did I verify the data exists in the files before searching?
  • Did I cite the file name in my output?
  • Did I avoid fabricating numbers that should have come from the file?

Example Usage

Task: Create a report on active property listings. Context: Massabama_active_listings.xlsx is attached.

Incorrect Approach:

  • Ignore the Excel file.
  • Search web for "Massabama property listings".
  • Fabricate numbers based on search snippets.
  • Result: Inaccurate data, ignored source of truth.

Correct Approach:

  • Identify Massabama_active_listings.xlsx in context.
  • Load the Excel file.
  • Count rows and sum prices directly from the sheet.
  • Output: "Based on the 50 entries in Massabama_active_listings.xlsx, the total value is..."
  • Result: Accurate data, verified source.

Warnings

  • Hallucination Risk: Ignoring provided files is a primary cause of data fabrication.
  • Efficiency: Reading a local file is faster and more reliable than web scraping.
  • User Expectation: Users attach files expecting them to be used. Ignoring them is a failure of instruction following.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

See all skills by HKUDS

Report a problem with this skill