agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/ai-opportunity-scan/SKILL.md

ai-opportunity-scan

Skill1 starsChanged 26 days agoMITView on GitHub

Finds and prioritises practical AI opportunities when a business needs an evidence-led starting point.

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.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use before an AI programme, workshop or investment decision to locate valuable, feasible and responsible use cases.

    line 9
  2. Distinctive:

    Place candidates on an impact-effort matrix and flag dependencies or controls.

    line 22
  3. Distinctive:

    Every use case begins with a verified business problem.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

AI Opportunity Scan

When to use it

Use before an AI programme, workshop or investment decision to locate valuable, feasible and responsible use cases.

What Claude needs

  • client-context.md for business background
  • A list of workflows, roles and recurring decisions
  • Current pain points, volumes and service expectations
  • Data sources, technology constraints and risk boundaries

Method

  1. Segment work into create, classify, extract, predict, decide and interact activities.
  2. Identify friction, judgement load, repeatability and data availability for each activity.
  3. Frame each opportunity with user, trigger, task, input, output and human oversight.
  4. Score value, feasibility, data readiness and harm exposure on defined scales.
  5. Place candidates on an impact-effort matrix and flag dependencies or controls.
  6. Select pilots with hypotheses, success measures, owners and stop conditions.

Output format

Provide an opportunity table with use case, user, problem, AI task, value, feasibility, risks and priority. Follow with pilot briefs and a do-not-pursue list.

Quality checks

  • Every use case begins with a verified business problem.
  • Scores use consistent definitions and cite available evidence.
  • Human oversight and failure consequences are explicit.

Download now (ZIP)

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.