agentleFS
javiarmestojaviarmesto/ALDC-AL-Development-Collection/skills/al-agent-instructions/SKILL.md

al-agent-instructions

Skill115 starsChanged 14 days agoMITView on GitHub

Generate optimized natural language instructions for Business Central agents (Designer or SDK). Applies the Responsibilities-Guidelines-Instructions framework from skill-agent-instructions. Output stored in .resources/Instructions/InstructionsV1.txt for SDK agents.

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:

    Start with navigation (how does the agent reach the data?)

    line 45
  2. Distinctive:

    Read and MEMORIZE context before decisions

    line 46
  3. Very specific:

    Run through the validation checklist from skill-agent-instructions.

    line 54

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Workflow: Generate Agent Instructions

Applies the Responsibilities-Guidelines-Instructions framework from skill-agent-instructions to produce a runtime-ready instruction file. This prompt does not contain the framework — it executes it.

Load skill first: skill-agent-instructions (framework, keywords table, validation checklist, anti-patterns).

Output modes

  • Designer mode → text ready to paste into the Agent Designer wizard
  • SDK mode → text stored in .resources/Instructions/InstructionsV1.txt, loaded via NavApp.GetResourceAsText() returning SecretText, applied via Agent.SetInstructions(UserSecurityId, InstructionsText)

Workflow

1. Gather inputs

From the developer:

  1. Agent purpose — one-sentence business goal
  2. Pages in scope — pages included in the agent's profile
  3. Fields to read/write — exact field names from those pages
  4. Actions to invoke — exact action captions on those pages
  5. Decision criteria — business rules for branching (if/then)
  6. Output format — how should the agent report results?
  7. Safety gates — which actions need user intervention?

2. Draft RESPONSIBILITY

One sentence with business domain + outcome. No paragraphs.

3. Draft GUIDELINES

3–7 cross-task rules. Required: at least one ALWAYS, one DO NOT, one safety gate for critical actions, one data-access boundary (read-only vs read-write).

4. Draft INSTRUCTIONS per task

For each task:

  1. Start with navigation (how does the agent reach the data?)
  2. Read and MEMORIZE context before decisions
  3. Apply business logic with explicit if/then branches
  4. Execute actions using proper keywords (see skill-agent-instructions keywords table)
  5. Report results with structured Reply format
  6. Include error handling at the end of the task

5. Validate

Run through the validation checklist from skill-agent-instructions. Key items:

  • Page/field/action names match agent profile exactly
  • MEMORIZE placed BEFORE value is needed in later steps
  • MEMORIZE includes example format
  • Critical actions gated by user intervention or review
  • Written in English
  • Environment-agnostic (no hardcoded company names, URLs, user IDs)
  • Error handling section per task
  • No references to "Tell Me"
  • Guidelines count is 3–7
  • Stored in .resources/Instructions/InstructionsV1.txt (SDK mode)

6. Test and iterate

Deploy → observe timeline → refine. Apply the "less is more" principle.

Reference

For the framework details, keyword tables, anti-patterns, and complete examples, consult skill-agent-instructions and .github/skills/skill-agent-instructions/examples/.

Skills Evidencing

End with:

**Skills loaded**: skill-agent-instructions
**Patterns applied**:
- RGI framework — Responsibilities/Guidelines/Instructions structure
- Keywords applied: {list keywords used: Navigate to, Memorize, Reply, etc.}
- Safety gates: {list user intervention / review points}

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.