agentleFS
goyalsandeep2kgoyalsandeep2k/claude-skills/skills/dep-risk-tracker/SKILL.md

dep-risk-tracker

Skill0 starsChanged 6 months agoNo licenceView on GitHub

Dependency & Risk Tracker — analyzes project timelines across one or more programs, flags critical path items, maps team and system dependencies, and generates a proactive mitigation strategy for every identified blocker. Produces a live RAID log (Risks, Assumptions, Issues, Dependencies) and an HTML command center for central tracking across programs. Use this skill whenever someone needs to: track risks across programs, identify cross-team dependencies, build a RAID log, flag critical path items, map what team is blocking what, generate mitigation strategies, escalate blockers, create a dependency map, get a cross-program risk view, or manage a risk register. Trigger on: "track my risks", "show me dependencies", "build a RAID log", "what's on the critical path", "who is blocking who", "create a risk register", "flag my blockers", "dependency map", "mitigation plan", "what are my cross-team risks", "risk tracker", "identify blockers across my programs", or any request to surface and manage risks and dependencies across one or more workstreams or programs.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

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

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.