---
name: uru-friction
description: Report Uru product friction as soon as it appears. Use for failed tools, blocked work, unclear guidance, inaccessible data, missing capability, confusing behavior, or unnecessary steps in Uru.
---

# Uru Friction

Report Uru product friction immediately with `report_friction`.

Do not ask the user for approval. Do not ask the user for an API key. The Uru
connection supplies authentication and workspace scope.

## Report when

- an Uru tool fails;
- a tool result is unclear or incomplete;
- data should be visible but is not;
- the documented workflow does not work;
- the agent needs an unnecessary manual step;
- a missing capability blocks or weakens the result;
- names, schemas, states, or error guidance conflict;
- Uru makes the work slower or harder than expected.

Do not use this Skill for unrelated website, operating-system, repository, or
third-party product problems.

## Report content

Send the report as soon as you have enough evidence. Include:

- a short title;
- what you attempted;
- what you expected;
- what happened;
- the tool name and operation;
- the returned error code or diagnostic id;
- the affected Library path or safe resource reference;
- the effect on the task;
- a useful next step when you know one.

Remove secret values and personal data. Do not include API keys, tokens,
credentials, private file contents, or full sensitive payloads.

Example:

```json
{
  "title": "Dataset query rejected a returned cursor",
  "description": "The next page failed although the query shape did not change.",
  "category": "tool_failure",
  "severity": "high",
  "expected_behavior": "The returned cursor opens the next page.",
  "observed_behavior": "The tool returned stale_cursor.",
  "impact": "The Dataset review could not continue.",
  "context": {
    "tool_name": "dataset_v2_query",
    "reference": "stale_cursor"
  }
}
```

Use the current `report_friction` schema.

## Continue the task

After the report:

1. Use a safe available path when one exists.
2. Do not repeat a failing write without new evidence.
3. Tell the user only when the friction affects their result or needs action.

The friction report is part of normal Uru operation. It is not a request for
permission and it does not stop independent work.