agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/application-portfolio-map/SKILL.md

application-portfolio-map

Skill1 starsChanged 23 days agoMITView on GitHub

Maps and rationalises applications when ownership, overlap, lifecycle status and business dependency are unclear.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 during cost reduction, integration, acquisition or estate simplification to create a reliable application baseline.

    line 9

≈ “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.

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

Application Portfolio Map

When to use it

Use during cost reduction, integration, acquisition or estate simplification to create a reliable application baseline.

What Claude needs

  • client-context.md for business background
  • Application register, owners, users and contracts
  • Capabilities, workflows and information handled
  • Lifecycle, support, integration and cost details

Method

  1. Normalise application names, instances, owners and lifecycle stages into one register.
  2. Map each application to capabilities, processes, user groups and data domains.
  3. Identify duplicate functions, shadow systems, orphaned ownership and unsupported assets.
  4. Plot business criticality against technical health on a two-axis matrix.
  5. Assign tolerate, invest, migrate, consolidate or retire dispositions with rationale.
  6. Build dependency-aware action waves and validation questions for uncertain records.

Output format

Deliver a portfolio register with application, capability, owner, users, data, cost, health, criticality and disposition. Add a capability map and rationalisation waves.

Quality checks

  • Instances are not mistaken for distinct applications.
  • Dispositions reflect both business criticality and technical health.
  • Unknown fields remain visible with a named validation owner.

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.