FabriXWork User GuideFabriXWork User Guide
Home
Getting Started
Use Cases
Best Practices
Why FabriXWork
Help
Home
Getting Started
Use Cases
Best Practices
Why FabriXWork
Help
  • Help & Troubleshooting

    • Help & Troubleshooting
    • Diagnostic Guide
    • Installation Issues
    • Login Issues
    • Agent Output Issues
    • Performance Issues
    • Technical FAQ

Agent Output Issues

Getting unexpected or incorrect results from your AI agents? This guide helps you diagnose and fix output quality problems.


Quick Fixes: Try These First

Fix 1: Be More Specific in Your Request

Vague instructions lead to vague outputs. Add more detail about:

  • What you want (specific format, structure, content)
  • Who it's for (audience)
  • How long it should be (length constraints)
  • Any examples or templates to follow

Fix 2: Provide Context

Agents perform better with background information:

  • Why you need this
  • What you'll use it for
  • Any relevant background or constraints

Fix 3: Iterate and Refine

First attempts aren't always perfect. Try:

  • "That's good, but can you make it more concise?"
  • "Add more detail to section 2"
  • "Reformat this as a table instead"

Fix 4: Check Your Files

If the agent is working with files:

  • Verify the files exist in the connected folder
  • Make sure files are readable (not corrupted)
  • Confirm the agent is looking at the right files

Common Output Issues

Issue: Output is Too Vague or Generic

Example:

You: "Write a report"
Agent: [Produces a generic template with placeholder text]

Why it happens:

  • Instruction lacks specificity
  • No context about audience or purpose
  • No format requirements given

Solutions:

Solution 1: Add Specific Requirements

Before: "Write a report"

After: "Write a Q1 marketing performance report for the executive team.
Include: campaign results, budget vs. actuals, key wins, and Q2 recommendations.
Format: 2-page summary with bullet points and a data table.
Tone: Professional and data-driven."

Solution 2: Provide Examples

"Write a status report similar to the one I shared last week.
Use the same structure and level of detail.
Focus on: completed tasks, blockers, and next steps."

Solution 3: Specify What to Include (and Exclude)

"Create a competitor analysis that includes:
- Company name, founding year, key products, pricing
- Exclude: companies founded before 2010
- Focus on: direct competitors in the SaaS project management space"

Issue: Output Contains Incorrect Information

Example:

Agent provides statistics or facts that are wrong

Why it happens:

  • Agent may be inferring from incomplete data
  • Source files may have outdated information
  • Agent may be "hallucinating" (making up) details

Solutions:

Solution 1: Provide Source Data

"Use ONLY the data from the Q1_Report.xlsx file in my Reports folder.
Do not infer or add numbers that aren't in the source file.
If data is missing, mark it as [DATA NOT AVAILABLE]."

Solution 2: Ask for Citations

"Include source references for all claims.
For each statistic, note which file and page it came from."

Solution 3: Request Verification

"Before finalizing, list all the key facts you're including.
I'll verify them before you generate the full output."

Solution 4: Fact-Check the Output

Always review agent output for accuracy:
- Cross-check numbers with source files
- Verify names, dates, and titles
- Confirm any external facts (if agent did research)

Issue: Output Format is Wrong

Example:

You asked for a table, got paragraphs
You asked for bullet points, got a wall of text

Solutions:

Solution 1: Be Explicit About Format

"Output as a markdown table with these columns: Name, Date, Amount, Status"
"Use bullet points, max 5 words per bullet"
"Format as JSON with these fields: ..."

Solution 2: Provide a Template

"Format the output like this example:

[Your example here]

Follow this exact structure."

Solution 3: Request Reformatting

"That content is good, but reformat it as:
- A table instead of paragraphs
- Bullet points instead of sentences
- JSON/CSV/XML format"

Issue: File Not Created or Saved

Example:

Agent says it saved a file, but you can't find it

Why it happens:

  • Wrong folder path
  • File saved with unexpected name
  • Agent doesn't actually have file write capability
  • Permission issues

Solutions:

Solution 1: Specify Exact Path

"Save the file to: /Users/yourname/Documents/Reports/
Filename: Q1_Summary.docx"

Solution 2: Verify Folder Access

1. Check the file panel in the chat interface
2. Confirm the folder is connected
3. Verify you have write permissions to that folder

Solution 3: Ask Agent to Confirm

"Before saving, confirm:
- The full path where you'll save
- The exact filename
- The file format"

Solution 4: Search for the File

1. Use Finder (macOS) or File Explorer (Windows)
2. Search for the filename or part of it
3. Check your Downloads folder (default save location)
4. Check the connected folder in FabriXWork

Issue: Agent Doesn't Understand My Request

Example:

Agent asks for clarification repeatedly
Agent seems confused about what you want

Solutions:

Solution 1: Break It Down

Instead of one complex request, break it into steps:

"Step 1: Read the files in my Research folder
Step 2: Identify the top 5 themes
Step 3: Create a summary for each theme"

Solution 2: Use Simple, Direct Language

Avoid: "Can you maybe sort of put together something about the thing?"
Use: "Create a one-page summary of Q1 sales results"

Solution 3: Ask Agent to Paraphrase

"Before you start, tell me what you understand this task to be."

Solution 4: Provide an Example

"Here's an example of what I'm looking for:
[Paste example]

Create something similar for [your topic]."

Issue: Output is Too Long or Too Short

Too Verbose:

Agent writes 5 pages when you needed 5 bullets

Solutions:

"Summarize in 3 bullet points, max 10 words each"
"Keep it under 200 words"
"One paragraph only"
"Executive summary format: 5 bullets max"

Too Brief:

Agent gives 2 sentences when you needed a full report

Solutions:

"Expand on each point with at least 2-3 sentences"
"Include examples for each claim"
"Add background context and detailed analysis"
"Write a comprehensive 2-page report"

Issue: Agent Ignores My Files

Example:

You connected files but agent doesn't use them

Solutions:

Solution 1: Explicitly Reference Files

"Read the file 'Q1_Data.xlsx' in my Reports folder.
Use the data from Sheet1 for your analysis."

Solution 2: Ask Agent to Confirm It Can See Files

"What files can you see in my connected folder?"

Solution 3: Check Folder Connection

1. Look at the file panel in the chat interface
2. Confirm files are visible
3. If not, reconnect the folder

Solution 4: Verify File Format

- Some file types may not be readable
- Common supported formats: TXT, DOCX, PDF, CSV, XLSX, JSON
- Proprietary or encrypted files may not work

Improving Output Quality

Tip 1: Use the ITERATE Method

I - Initial request
T - Test the output
E - Evaluate what's missing
R - Refine your instruction
A - Ask for specific changes
T - Try again
E - Evaluate and repeat

Example:

You: "Create a competitor list"
Agent: [Basic list with names only]

You: "Good start. Add founding year and headquarters location for each"
Agent: [Adds requested info]

You: "Perfect. Now add a column for their main product and pricing tier"
Agent: [Complete table]

Tip 2: Provide Quality Examples

"Here are two examples of good [output type]:

Example 1:
[Paste example]

Example 2:
[Paste example]

Create something similar in style and quality."

Tip 3: Set Clear Constraints

Constraints improve focus:
- "Use only data from 2025 or later"
- "Focus on enterprise customers only"
- "Exclude anything marked as confidential"
- "Maximum 500 words"

Tip 4: Ask for Multiple Options

"Give me 3 different versions:
1. Conservative/formal tone
2. Friendly/casual tone
3. Persuasive/sales tone

I'll choose the best one."

Tip 5: Request Self-Review

"Before finalizing, review your output and:
1. Check for accuracy
2. Ensure all requirements are met
3. Identify any gaps or missing information
4. Suggest improvements"

Prompt Templates for Better Output

Template 1: Structured Report

Create a [TYPE OF REPORT] about [TOPIC].

Audience: [WHO WILL READ THIS]
Purpose: [WHY THEY NEED IT]

Required sections:
1. [Section 1]
2. [Section 2]
3. [Section 3]

Format: [FORMAT - bullets, paragraphs, table, etc.]
Length: [APPROXIMATE LENGTH]
Tone: [TONE - professional, casual, technical]

Use data from: [SPECIFIC FILES/FOLDERS]

Template 2: Data Analysis

Analyze the data in [FILE/FOLDER].

Objective: [WHAT YOU WANT TO LEARN]

Tasks:
1. [First analysis step]
2. [Second analysis step]
3. [Third analysis step]

Output format: [TABLE/CHART/SUMMARY]

Include:
- Key findings
- Trends identified
- Anomalies or outliers
- Recommendations (if applicable)

Template 3: Content Creation

Create [CONTENT TYPE] about [TOPIC].

Context:
- [Background information]
- [Key messages to include]

Requirements:
- Length: [X words/pages/slides]
- Audience: [WHO]
- Tone: [TONE]

Structure:
- [Outline or key sections]

Include:
- [Specific elements required]

When to Switch Agents

If you're consistently getting poor output:

Try a different agent:

  • Some agents specialize in different tasks
  • Alex (Business Analyst) → Structured reports, analysis
  • Rookie (Intern) → General tasks, research
  • Claire (Claims Specialist) → Document analysis
  • Audrey (Audit Agent) → Compliance, detail-oriented tasks

Still Not Getting Good Results?

Step 1: Review Your Instructions

  • Are they specific enough?
  • Did you provide context?
  • Is the format clearly defined?

Step 2: Check Your Source Files

  • Are they accessible to the agent?
  • Is the data complete and accurate?
  • Are they in a readable format?

Step 3: Iterate More

  • Don't settle for the first output
  • Provide feedback and ask for revisions
  • Break complex tasks into smaller steps

Step 4: See Examples

  • Review Best Practices
  • Check Use Cases for working examples
  • Try the copy-paste prompts from use cases

Related:

  • Best Practices - Improve your prompts
  • Interact with an Agent - Communication basics
  • Use Cases - See working examples
Prev
Login Issues
Next
Performance Issues