agentleFS
Sign inStart free
latour-ailatour-ai/skills/ai-workflow-audit/SKILL.md

ai-workflow-audit

Skill69 starsChanged 24 days agoNo licenceView on GitHub

Interview a team about their recurring workflows, bottlenecks, data sources, and tools — one question batch at a time — then map the workflows to AI opportunities scored on impact × feasibility and deliver a prioritized AI adoption roadmap with quick wins, skill candidates to build, and risks. For investment firms and professional teams of any function. Trigger on phrases like "audit our workflows for AI," "where should we use AI," "AI opportunity assessment," "interview me about our processes," "help us figure out what to automate," "AI readiness review," "build our AI roadmap," or "which of our tasks should AI do." Do NOT use for generating specific skill ideas from an already-known workflow — use the investment-skill-creator skill. Do NOT use for learning what AI can do in general — use the teach-me skill.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free