playbooks

home / skills / bdambrosio / cognitive_workbench / refine

refine skill

/src/tools/refine

This skill redirects to the extract tool for backward compatibility, ensuring seamless access while transitioning to the preferred workflow.

npx playbooks add skill bdambrosio/cognitive_workbench --skill refine

Review the files below or copy the command above to add this skill to your agents.

Files (2)
Skill.md
346 B
---
name: refine
type: python
flattens_collections: true
hidden: true
description: "DEPRECATED — use extract instead. Routes to extract tool for backward compatibility."
---

# refine (DEPRECATED)

**Use `extract` instead.** This tool is a backward-compatibility wrapper that routes to `extract`.

See `extract` documentation for full details.

Overview

This skill is a deprecated compatibility wrapper that routes calls to the newer extract tool. It exists to preserve older integrations while directing traffic to the current implementation. Users should migrate to extract for full-featured support and future updates.

How this skill works

When invoked, the skill forwards requests and parameters to the extract tool and returns the extract tool's response. It does not implement independent extraction logic or new features; it only maps inputs to the extract interface. Error handling and behavior follow the extract tool's implementation.

When to use it

  • Maintaining legacy integrations that still reference the refine endpoint.
  • Quick compatibility during a migration period from refine to extract.
  • Automated systems that cannot be updated immediately but need continued functionality.
  • Testing that verifies older calls still resolve correctly to the new implementation.

Best practices

  • Plan and execute migration to the extract tool to get bug fixes and new features.
  • Replace refine references in code, docs, and automation as part of regular maintenance.
  • Treat refine as a temporary shim; do not build new functionality on top of it.
  • Verify that parameters sent to refine match the extract tool's expected inputs.

Example use cases

  • A legacy service that calls refine continues working while you update the client to call extract.
  • A CI pipeline that validates endpoint compatibility by asserting refine routes to extract.
  • Documentation snapshots that still list refine but link users to extract for current behavior.

FAQ

Is refine still receiving updates?

No. refine is deprecated and maintained only as a routing shim. Use extract for updates and support.

Can I rely on refine long-term?

No. You should migrate to extract because refine may be removed in the future and will not receive new features.