FICTIONAL EXAMPLE. The organisation, documents, figures and events are invented.

Worked example: a skill for a credit committee memo

Organisation settings (fictional)

The brief (fictional)

A credit analyst answers the ten questions: credit memo; template headings Facility, Borrower, Financials, Risks, Recommendation; reviewer checks covenants first; only the Credit Policy v12 and the file; sign-off Senior Analyst then Credit Manager; Restricted allowed; refuses to assign a rating; owner Head of Credit; both products; invented example.

DRAFT. Prepared with corporate-skill-maker v1.0.0. Not approved.

Part A: the skill (first lines)

Name: credit-memo. Version 1.0.0.

Control. Owner: Head of Credit. Sign-off: Senior Analyst, then Credit Manager. Classification note: credit files are Restricted; no customer data in examples. Highest allowed here: Restricted.

What to produce. Facility. Borrower. Financials. Risks. Recommendation. (In that order, as in the bank's template.)

Before delivering. Covenants are stated first in Risks, because the reviewer looks there first. Every number has a source tag.

Stop or refuse when. Asked to assign a credit rating. The rating comes from the rating system; this skill copies it, with its source.

Part B: the agent files

declarativeAgent.json and manifest.json as specified. No capabilities or actions. The developer web pages stay [FILL IN] until IT supplies them.

Part C: the security review sheet

ItemAnswer
ScriptsNone
Web addressesOnly the three [FILL IN] items in manifest.json
Actions, plugins, toolsNone declared
Web searchNot declared
Knowledge sourcesCredit Policy v12, and the file the analyst pastes
Highest classificationRestricted
Processing locationCopilot service under the existing agreement: IT to confirm
What it cannot enforceCopilot's own tools and web settings: these need admin settings
TestedInvented memo, result attached
DecisionTechnology Risk Partner: ____ Date: ____

This sheet supports a review. It is not a certification.