repairing-workspaces-agents

Repair broken Friday workspaces, jobs, and agents to match runtime contracts.

97|5|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/friday-platform/friday-studio --skill repairing-workspaces-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repairing-workspaces-agents
Source: https://github.com/friday-platform/friday-studio/tree/main/packages/system/skills/repairing-workspaces-agents
Command: npx skills add https://github.com/friday-platform/friday-studio --skill repairing-workspaces-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves failures in existing Friday workspaces, jobs, user agents, and generated agents caused by platform upgrades, outdated configurations, missing tool access, empty output emissions, or broken human-in-the-loop (HITL) flows, eliminating the need to rebuild functional workflows from scratch.

Core Features & Use Cases

  • Structured Repair Workflow: Follow a step-by-step checklist to diagnose failures, identify the broken runtime contract boundary, and apply minimal targeted fixes to preserve original workflow intent.
  • Common Failure Resolution: Fixes outdated verb-first tool names, missing output emissions for outputTo actions, broken HITL flows that rely on chat menus instead of platform primitives, and Python agents that bypass host tool capabilities.
  • Use Case: If your scheduled inbox triage job stopped working after a Friday platform update, or your custom Python agent can no longer call Gmail tools, use this Skill to restore full functionality without rebuilding the entire workflow.

Quick Start

Use this skill to diagnose and fix your failing Friday workspace job that stopped producing output after a recent platform upgrade.

Frequently Asked Questions about repairing-workspaces-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a Friday workspace job that stopped working after a platform upgrade?

Fix a broken Friday workspace job by running a structured diagnosis to locate the broken runtime contract boundary, then applying minimal targeted fixes that preserve the original workflow intent without rebuilding from scratch.

Why does my Python agent no longer have access to host tools like Gmail?

Python agents lose host tool access when they bypass platform capabilities or use outdated configurations; repairing the agent's runtime contract restores authorized tool access and normal execution.

How do I repair broken human-in-the-loop flows in my Friday workspace?

Repair broken human-in-the-loop flows by replacing outdated chat menu dependencies with current platform primitives, then validating the corrected HITL flow through the daemon.

What causes empty action outputs in Friday jobs and how do I resolve them?

Empty action outputs occur when missing output emissions for outputTo actions fail to meet current runtime contracts; resolving this requires diagnosing the output boundary and applying targeted fixes.

Do I need to rebuild my entire workflow if a Friday platform update breaks my agent?

No, you do not need to rebuild; the repair workflow applies minimal targeted fixes to broken workspaces and agents while preserving the original workflow intent and avoiding non-user-visible compatibility shims.