Skip to content
cccskills
FreePublished on GitHub

compliance-escalation-brief

Prepare a neutral brief for counsel or the security lead on a matter that needs their judgement.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (1)

  • SKILL.md1.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Compliance escalation brief

Use this whenever a matter needs a legal or security judgement.

Decide if it must escalate

Escalate to counsel when the matter touches a possible breach or incident, regulator contact, legal basis, liability or indemnity terms, a request you cannot scope, or a claim the company cannot back with evidence. Escalate to the security lead for control failures or unclear technical facts. When in doubt, escalate.

Write the brief

Put the decision first:

  1. the exact question for counsel or the security lead;
  2. the deadline and what depends on it;
  3. the facts, with times and sources;
  4. the documents involved, with version and section;
  5. the company's supplied position or checklist, quoted;
  6. what is not yet known;
  7. the business owner and who else knows.

Keep facts, claims from others, and open questions apart. Attach the source rather than a fragment when context matters.

What you did not decide

State plainly what the brief leaves open: whether the matter is reportable, whether a clause is acceptable, and what to tell the other side.

Do not give legal advice, say whether the company is compliant, or advise on breach notice. Return an unsent draft; counsel decides and an authorised person sends.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Write ad variants that each test one idea, within platform limits and supported claims.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

The English summary is being prepared. Showing the original description.

Significant-Gravitas/skills-catalog2Updated Oct 22, 2026

See all skills by Significant-Gravitas

Report a problem with this skill