agentleFS
vpeetla-aivpeetla-ai/multi-agent-system-pattern/.cursor/skills/portfolio-adr/SKILL.md

portfolio-adr

Skill2 starsChanged 5 months agoMITView on GitHub

Write ADRs, case studies, and portfolio copy for ai-architecture-portfolio and venkat-ai-portfolio. Use when documenting decisions, updating ecosystem pages, or syncing GitHub profile README with live demos.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No fake metrics; cite eval gates and test counts instead

    line 43
  2. Distinctive:

    Verify all demo URLs return 200

    line 59
  3. Very specific:

    Update stack map in ecosystem.ts if layer changed

    line 60

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

Portfolio & ADR Writing

ADR template

# ADR-NNN: Title

## Status
Proposed | Accepted | Superseded

## Context
What problem and constraints?

## Decision
What we chose.

## Consequences
Trade-offs, what we gave up.

## Links
Live demo, repo, related ADR

Case study structure

  1. Problem (1 paragraph)
  2. Architecture diagram (mermaid or link)
  3. Key decisions (3–5 bullets with ADR links)
  4. Live demo URL (must work)
  5. What we'd do differently

Honesty rules

  • Implemented vs Planned vs Demo-only — separate columns in README tables
  • No fake metrics; cite eval gates and test counts instead

Sync targets

ArtifactRepo
ADRs, case studiesai-architecture-portfolio
venkat-ai.com pagesvenkat-ai-portfolio
GitHub profilevpeetla-ai/README.md

Essay anchor

from-multi-agent-os-to-agent-governance — link from profile + portfolio

After writing

  • Verify all demo URLs return 200
  • Update stack map in ecosystem.ts if layer changed

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.