agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/copilot-agent-inventory-samples/samples/agent-warden/skills/change-log/SKILL.md

change-log

Skill29 starsChanged 29 days agoMITView on GitHub

Maintain a running audit trail of every governance action Warden performs. After each successful block/unblock/reassign, append a row to a change-log file capturing the agent, the action, the before/after state, and a timestamp. Use to keep a reviewable record and to satisfy "what changed and when" questions.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. M-Bajalan/kibsu-lab★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Only log an action after the Package Management write returns success — never pre-emptively.

    line 39
  2. Very specific:

    If the inventory-list write-back failed, record ListSynced = no so the discrepancy is visible.

    line 40

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

change-log

When to use

Invoke immediately after any successful governance write (block, unblock, reassign availability/deployment, reassign owner), and whenever the admin asks "what changes have been made" or wants an exportable audit trail.

Inputs

  • The outcome of the action just performed (agent id + name, action, resolved before/after audience or blocked flag).
  • An existing warden-change-log.csv if one has already been produced in the session, so new rows are appended rather than overwriting.

What it does (runs code)

Using CodeInterpreter, create the log on first use or modify the existing file on subsequent actions, appending one row:

ColumnMeaning
TimestampUTC time the action completed
AgentIdThe agent's Agent Id
NameDisplay name
ActionThe action taken
BeforeResolved prior state (blocked flag or audience names)
AfterResolved new state
Resultsucceeded / failed
ListSyncedWhether the inventory-list write-back succeeded

Outputs

  • warden-change-log.csv (created once, then appended in place across the session).

Notes / constraints

  • Only log an action after the Package Management write returns success — never pre-emptively.
  • If the inventory-list write-back failed, record ListSynced = no so the discrepancy is visible.
  • This skill records history; it does not perform or retry governance actions.

Status

Draft stub — not yet referenced by the agent.

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.

Check your setup, free