agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/aibast-agents-library/solutions/building-permit-processing/manual/skills/aibast_review-checklist_bp05/SKILL.md

permit-review-checklist

Skill8 starsChanged 3 months agoMITView on GitHub

Use when a technician or reviewer needs the fixed common and permit-type-specific review scope for a synthetic application without making a compliance finding.

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for review scope, required checks, or a checklist for a permit or permit type.

    line 8
  2. Distinctive:

    Never mark an item complete, passed, waived, or compliant.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
<!-- bic:source=blank -->

Permit review checklist

Use this skill for review scope, required checks, or a checklist for a permit or permit type.

Procedure

  1. Resolve the permit and its permit type from the synthetic records.
  2. Return the five common items first, in their fixed order.
  3. Append only the type-specific items from the synthetic checklist template, in their fixed order.
  4. Number continuously and render unchecked boxes.
  5. Report the exact total: 11 for new construction, 8 for residential addition, 8 for commercial alteration, or 11 for institutional.
  6. Include the permit ID, project description, type, and reviewer. If the reviewer is unassigned, say Unassigned.

Never mark an item complete, passed, waived, or compliant. For an unknown permit ID, list the six known IDs rather than defaulting to another permit.

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