cidf

Selects the lowest-complexity eligible method for content insertion tasks with linting and verified fallback execution.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill cidf-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cidf
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/cidf
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill cidf-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agents routinely over-engineer content insertion by jumping to scripts when a simple form input or paste would work, and they mark tasks complete based on unreliable visual confirmation. This Skill replaces ad hoc judgment with a deterministic, testable decision procedure for inserting content into documents, web forms, and editors. ## Core Features & Use Cases - Ranked method selection: The decide() function always starts at the lowest-complexity eligible method (form input, typing, paste, upload) and only appends scripting as a last-resort fallback when the automation gate is open. - Pre-execution linting: lint_strict() enforces rules LINT-001 through LINT-008, blocking premature scripting, disabled verification, complexity bias, and unsafe content such as absolute workstation paths or mojibake. - Verified execution with fallback: execute_with_fallback() runs the chosen chain and confirms success only via a programmatic signature check, never visual confirmation, with a blocked-decision path that notifies the user when no method is eligible. - Use Case: An agent must insert a 2,000-character article into a CMS field. It calls decide() with the task and environment, receives direct_form_input with paste as fallback, lints the decision, executes, and verifies the signature in extracted page text before marking the task complete. ## Quick Start Ask the agent to decide and execute the correct insertion method for your content using the CIDF decide, lint, and execute_with_fallback API with a verification signature.

Frequently Asked Questions about cidf

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

FAQPage Schema
How do I decide which method to use for inserting content with an AI agent?

Call the decide() function with a Task describing the content and an Env describing available methods. It returns the lowest-complexity eligible tool, starting with direct form input, then typing, paste, upload, and scripting only as a gated last resort.

When is scripting justified for content insertion tasks?

Scripting is justified only when the automation gate is open: frequency of 5 or more runs, conditional logic, transformation, or external integration required. It is hard-blocked for one-time static content or when setup time exceeds run time.

Can I use this framework with LangChain or CrewAI agents?

Yes. The core Python library is framework-agnostic, and the documentation shows how to wrap decide() as a LangChain tool and share it across CrewAI agents. A TypeScript port supports Node.js integrations such as OpenClaw.

Why does visual confirmation fail for verifying content insertion?

Pages lag and caches lie, so a UI that appears unchanged may still contain the content. The framework requires programmatic verification: refresh once, extract text, and confirm the task signature is present before marking complete.

What happens when no insertion method is eligible?

decide() returns a blocked decision with a notification reason instead of inventing an unavailable tool. execute_with_fallback() then returns a blocked status so the caller notifies the user rather than attempting scripting with a closed gate.