agentleFS
PaulDanielYoungPaulDanielYoung/internal-audit-skills/skills/foundations/create-engagement/SKILL.md

create-engagement

Skill2 starsChanged 41 days agoMITView on GitHub

Create an engagement record from an engagement name and audit objective statement. Use when an auditor starts a new engagement or asks to create or set up an audit.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create the workspace structure and engagement record for an audit engagement.

    line 8
  2. Distinctive:

    Use the engagement name, objective statement, and year already clearly established in the context or conversation.

    line 31
  3. Distinctive:

    Use the engagement year and the engagement name in kebab-case (lowercase words joined by hyphens) to form the engagement folder path:

    line 35
  4. Very specific:

    Create engagements/, the year folder, and the engagement folder if they do not exist.

    line 39
  5. Very specific:

    Create ENGAGEMENT.md using the structure in ENGAGEMENT-FORMAT.md, replacing each comment with the engagement's content.

    line 43
  6. Distinctive:

    Create any missing directories from the File structure section above.

    line 44

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

Create Engagement

Create the workspace structure and engagement record for an audit engagement.

File Structure

Each engagement uses the following structure:

/
└── engagements/
    └── <year>/
        └── <name>/
            ├── ENGAGEMENT.md
            ├── document-requests/
            ├── fieldwork/
            ├── planning/
            ├── reporting/
            └── walkthroughs/

1. Establish the engagement name, objective, and year

Require a name, an objective statement, and a year: what the engagement is called, what it intends to accomplish, and the year it is planned for.

Use the engagement name, objective statement, and year already clearly established in the context or conversation. If any are missing or ambiguous, propose them and ask the auditor to confirm or revise.

2. Create the engagement workspace

Use the engagement year and the engagement name in kebab-case (lowercase words joined by hyphens) to form the engagement folder path:

engagements/<year>/<name>/

Create engagements/, the year folder, and the engagement folder if they do not exist. Otherwise, use the existing folders.

Within the engagement folder:

  • Create ENGAGEMENT.md using the structure in ENGAGEMENT-FORMAT.md, replacing each comment with the engagement's content. If the file already exists, leave it unchanged and report the conflict to the user.
  • Create any missing directories from the File structure section above. Leave existing directories unchanged.

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.