unknown-task

Apply a conservative fallback with a 15-tool-call budget for unmatched tasks.

6|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FRIKKern/doey --skill unknown-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unknown-task
Source: https://github.com/FRIKKern/doey/tree/main/.claude/skills/unknown-task
Command: npx skills add https://github.com/FRIKKern/doey --skill unknown-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a conservative fallback for tasks that do not match any specific skill, enabling safe execution when the exact skill is unknown.

Core Features & Use Cases

  • Conservative execution strategy with a strict maximum tool-call budget to minimize risk.
  • Explicit handling of ambiguity with required state and assumptions.
  • Prevents destructive actions and promotes minimal, verifiable edits.

Quick Start

When an input task has no matching skill, apply this fallback with a strict 15-tool-call budget and conservative edits.

Frequently Asked Questions about unknown-task

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

FAQPage Schema
How do I ensure safe AI execution when a task matches no specific skill?

A tool-call budget limits AI execution by capping the maximum number of tool invocations, up to 15 calls, during unknown tasks. This conservative execution strategy minimizes risk and prevents runaway actions when no matching skill is found.

What is a tool-call budget in conservative execution workflows?

A tool-call budget limits AI execution by capping the maximum number of tool invocations, up to 15 calls, during unknown tasks. This conservative execution strategy minimizes risk and prevents runaway actions when no matching skill is found.

How do I prevent destructive actions during ambiguous AI workflows?

Explicitly stating assumptions before acting provides clear context for ambiguous tasks, ensuring the AI operates safely under strict tool-call budgets. This conservative approach prevents destructive actions and promotes minimal, verifiable edits when handling unknown tasks.

Why does stating assumptions before acting improve AI guardrails?

Explicitly stating assumptions before acting provides clear context for ambiguous tasks, ensuring the AI operates safely under strict tool-call budgets. This conservative approach prevents destructive actions and promotes minimal, verifiable edits when handling unknown tasks.

Can I use a fallback skill for tasks with no matching skill?

This fallback approach limits AI to a maximum of 15 tool calls per task and requires stating assumptions before acting. It is designed for conservative execution of unknown tasks and does not support or permit destructive actions.

What are the limitations of using a strict tool-call budget for AI workflows?

This fallback approach limits AI to a maximum of 15 tool calls per task and requires stating assumptions before acting. It is designed for conservative execution of unknown tasks and does not support or permit destructive actions.