agentsclimarketplace

Fde discover workflow

Skill inbusiness23/fde-skill/skills/fde-discover-workflow

Privacy-safe forward-deployed engineering skills for Claude Code, Codex, and AGENTS.md-compatible agents

Install
npx -y skills add inbusiness23/fde-skill --skill fde-discover-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 16 days oldThe repository was created 16 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Learn how a workflow really operates and improve it before choosing technology. Use to define one measurable problem, name an owner, measure the baseline, find the primary cause, redesign the process, and decide whether AI is actually needed.

SKILL.md

2.0 KB, 365 tokens by cl100k_base, as published. Nobody here has run it

Learn and Improve the Process

Use plain language. Explain any necessary technical word immediately.

Steps

  1. Turn the request into one business result people can measure. Name the numbers that must not get worse.
  2. Name the person responsible, the employees doing the work, the people receiving it, and anyone harmed by a mistake.
  3. Read the written rules, then observe real cases, including workarounds and unusual cases.
  4. Measure volume, total time, staff minutes, completed sales or jobs, mistakes, rework, returns, and money made or lost.
  5. Test the likely cause: demand, information, process, rules, disconnected tools, training, capacity, hard judgment, or staff adoption.
  6. For every major step ask, in order: remove it, change it, make it easier, use simple rules, use an AI helper, or leave it with a person?
  7. Draw the better process, including what starts it, who owns each step, which tools are used, approvals, unusual cases, manual backup, and the end.
  8. Get clear approval from the business owner and a frontline employee.

Evidence rules

  • Separate facts, calculations, staff statements, and guesses.
  • Written instructions do not prove that staff follow them.
  • Use organization numbers instead of industry averages when available.
  • Treat “no AI needed” as a successful answer.
  • Ask only for the smallest extra evidence needed when information is missing.

Read workflow-assessment.md for the worksheet.

Return

Return the result, owner, facts, starting numbers, main cause, decision for each step, better process, missing evidence, and ready_for_next_step or blocked. Do not recommend AI until the owner approves the better process.

What ships with it: 2 files

1.4 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.