Msgraph
codemie-ai/codemie-code
Work with Microsoft 365 services via the Graph API — emails, calendar events, SharePoint sites (read and write), Teams chats and channel messages, OneDrive files, OneNote notebooks, Planner task…
Guidance for Microsoft Purview Records Management — declaring, managing, and disposing records across SharePoint, OneDrive, Exchange, and Teams.
Install Purview Records Management
$ npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills purview-records-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/purview-records-management .claude/skills/purview-records-management && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "purview-records-management" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/purview-records-management into .claude/skills/purview-records-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "purview-records-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/purview-records-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills purview-records-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/purview-records-management .agents/skills/purview-records-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "purview-records-management" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/purview-records-management into .agents/skills/purview-records-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "purview-records-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills purview-records-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/purview-records-management .cursor/skills/purview-records-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "purview-records-management" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/purview-records-management into .cursor/skills/purview-records-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "purview-records-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vinayaklatthe/microsoft-security-skills.git --path skills/purview-records-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills purview-records-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/purview-records-management .gemini/skills/purview-records-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "purview-records-management" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/purview-records-management into .gemini/skills/purview-records-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "purview-records-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vinayaklatthe/microsoft-security-skills purview-records-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/purview-records-management .github/skills/purview-records-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "purview-records-management" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/purview-records-management into .github/skills/purview-records-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "purview-records-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vinayaklatthe/microsoft-security-skills purview-records-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/purview-records-management .opencode/skills/purview-records-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "purview-records-management" agent skill from https://github.com/vinayaklatthe/microsoft-security-skills/tree/main/skills/purview-records-management into .opencode/skills/purview-records-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "purview-records-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
purview-records-management- GitHub stars
- 175
- Token cost
- ~2.2k tokens
- SKILL.md length
- 869 words
- Files
- 1
- Skills in repo
- 50
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guidance for Microsoft Purview Records Management — declaring, managing, and disposing records across SharePoint, OneDrive, Exchange, and Teams.
- Works in 8 steps: Get the file plan first. Records… → Define events for event-based retention.… → Publish vs auto-apply retention label… → …
- Non-records data lifecycle (use purview-data-lifecycle)
- SKILL.md covers When to use, Retention label flavors — pick…, Approach and Guardrails, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Purview Records Management is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Purview Records Management — declaring, managing, and disposing records across SharePoint, OneDrive, Exchange, and Teams. Covers retention labels with record / regulatory record options, file plan import, event-based retention (employee leaves, contract expires), disposition review (single- and multi-stage), proof of deletion / records of disposition, retention label policies vs auto-apply policies (KQL/sensitive info types/trainable classifiers), label-aware DLP, integration with…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office, covering Cloud office suites. It works with Microsoft SharePoint, Microsoft Sentinel and Microsoft OneDrive. The repository describes itself as: Curated Microsoft Security skills for AI agents - Defender, Sentinel, Entra, Purview, Intune, Security Copilot. The licence is MIT.
When your agent uses it
- Non-records data lifecycle (use purview-data-lifecycle)
- DLP policies (use purview-dlp-policy)
- EDiscovery (use purview-ediscovery)
Example prompts
- “/purview-records-management”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Get the file plan first. Records Management without a file plan is just labels
- Define events for event-based retention. Common events
- Publish vs auto-apply retention label policies.
- Pilot in a single SharePoint site / mailbox set. Validate that
- Disposition review. For records nearing end-of-retention, the Disposition
- Role separation.
- Reporting + audit. Pull disposition reports monthly. Stream to Sentinel or a
- Integrate with eDiscovery and Information Barriers. Records can still be subject
What it can do on your machine
Read from SKILL.md and the folder at commit 15f16df. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
learn.microsoft.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Purview Records Management loads about 2.2k tokens when it runs. Until then it costs about 255 tokens; SKILL.md has 869 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vinayaklatthe/microsoft-security-skills at commit 15f16df, republished under its MIT licence (© vinayaklatthe). 869 words, ~2,184 tokens.
Download SKILL.mdSave it as
.claude/skills/purview-records-management/SKILL.md (or your agent's skills folder).- name
- purview-records-management
- description
- Guidance for Microsoft Purview Records Management — declaring, managing, and disposing records across SharePoint, OneDrive, Exchange, and Teams. Covers retention labels with record / regulatory record options, file plan import, event-based retention (employee leaves, contract expires), disposition review (single- and multi-stage), proof of deletion / records of disposition, retention label policies vs auto-apply policies (KQL/sensitive info types/trainable classifiers), label-aware DLP, integration with Information Governance vs Records Management licensing, and role separation between records managers and admins. WHEN: records management Purview, file plan, retention label record, regulatory record, event-based retention, disposition review, record declaration SharePoint, immutable records, audit-proof deletion, file plan import. DO NOT USE for non-records data lifecycle (use purview-data-lifecycle), DLP policies (use purview-dlp-policy), or eDiscovery (use purview-ediscovery).
- license
- MIT
- metadata.author
- Microsoft
- metadata.version
- 0.1.0
Microsoft Purview Records Management
Records Management is the formal, auditable side of data lifecycle in Microsoft 365. Where general retention manages bulk data lifecycle, Records Management declares specific content as a record (cannot be modified or deleted) or regulatory record (immutable, no label change allowed once applied) and produces proof of disposition — the artefact regulators and auditors actually ask for.
When to use
You have legal, regulatory, or industry obligations (SEC 17a-4, GxP, GDPR Article 30, public-sector records acts) that require provable record retention and defensible disposition workflows.
Do not use this skill for general retention without record declaration
(purview-data-lifecycle), DLP (purview-dlp-policy), or eDiscovery
(purview-ediscovery).
Retention label flavors — pick deliberately
| Label option | Mutability | Disposition |
|---|---|---|
| Retention only (no record) | Editable | Auto-delete or do nothing |
| Record | Locked from edits/deletes; admin can unlock | Disposition review optional |
| Regulatory record | Fully immutable; label cannot be removed even by admin | Always disposition-reviewed |
| Unlock the record (admin action) | Reverts to standard label | — |
Rule of thumb: Use regulatory record only where the regulation truly demands WORM-style immutability (broker-dealer, life sciences GxP). Otherwise record is usually right — same protection, with an admin-unlock break-glass.
Approach
Get the file plan first. Records Management without a file plan is just labels sprawled across SharePoint. Source the file plan from Legal/Records team — typically a CSV with: label name, description, retention period, trigger (creation date / last modified / event), record/regulatory record flag, disposition action, business unit. Import via file plan manager.
Define events for event-based retention. Common events:
- Employee separation (HRIS connector or scripted Graph trigger).
- Contract expiry (CLM system event).
- Project closure.
- Product end-of-life. Events fire via Microsoft Graph or the compliance UI; retention countdown begins on event date.
Publish vs auto-apply retention label policies.
- Publish = label appears in user pickers; users tag content. Use for SharePoint document libraries with known content classes.
- Auto-apply = system applies based on KQL, sensitive info types, or trainable classifiers. Use for high-volume / known-pattern content (invoices, contracts).
Pilot in a single SharePoint site / mailbox set. Validate that:
- Labeled documents lock as expected.
- Edit attempts are blocked.
- Co-author scenarios (Teams files) still work.
- Retention countdown matches plan.
Disposition review. For records nearing end-of-retention, the Disposition queue presents items to reviewers (single or multi-stage). Reviewers can: dispose (delete with audit), relabel (extend retention), or hold (pending litigation). Records of disposition are retained — that's the audit artefact.
Role separation.
- Records Management role group: file plan, labels, disposition decisions.
- Compliance Administrator: configures the service, not the records.
- Reviewer (Disposition): per-label disposition reviewers. Records managers should not be tenant Global Admins.
Reporting + audit. Pull disposition reports monthly. Stream to Sentinel or a compliance system of record. Maintain the chain of custody artefact.
Integrate with eDiscovery and Information Barriers. Records can still be subject to legal hold; Information Barriers don't override retention. Confirm precedence rules with Legal.
Show full SKILL.md (399 more words)Show less
Guardrails
- Records Management is a separately licensed add-on (Microsoft 365 E5 Compliance / E5 Information Protection & Governance). Confirm licensing per-user — auto-apply on unlicensed users silently fails.
- Regulatory record is irreversible. Once a doc is labeled regulatory record, no one — including a tenant Global Admin — can change or remove the label. Pilot with test content only.
- Event-based retention needs a reliable event source. Don't fire termination events from a flaky integration; you'll over-retain or under-retain forever.
- Don't auto-apply records broadly with weak KQL. Mass-labeling production sites as records bricks the user experience (no edits).
- Co-authoring + record label combinations have caveats. Test in Teams/SharePoint before mass rollout.
- Disposition queues need owners. Without active reviewers, items sit at end-of- retention indefinitely, defeating the disposition story.
- Retention wins over deletion. A user "deleting" a record just hides it from view; it's preserved in the preservation hold library. Set expectations.
- Don't conflate retention and backup. Retention preserves the live data in M365; it's not a tenant restore plan.
Common anti-patterns
- "Imported file plan with 800 labels" — users see a giant picker, label nothing correctly. Start with the 10-20 most important records.
- "Used regulatory record by default 'to be safe'" — operational nightmare on first mistake.
- "Auto-apply records via 'contains the word contract'" — labels every email signature mentioning contracts as a record. Use sensitive info types or trainable classifiers.
- "Disposition queue ignored for 12 months" — retention extended by default; audit finding.
- "Records Management admin = Global Admin" — segregation-of-duties violation in regulated industries.
- "Skipped event-based retention because 'all records use creation date'" — over- retention on long-tail content; cost and risk.
- "Records Management used for backup" — wrong tool; restore scenarios still need proper backup.
Example prompts
Roll out Purview Records Management for SEC 17a-4 compliance with 6-year regulatory record retention on broker communications.Import a 60-label file plan from the records team and pilot on 3 SharePoint sites.Configure event-based retention: employee separation from Workday triggers a 7-year HR records hold.Design the disposition review workflow with 2-stage approvals: business owner then records manager.Compare retention label, record, and regulatory record for our contract management scenario.Integrate Records Management with our existing eDiscovery Premium holds for active litigation matters.Build the audit-of-disposition export to feed our GRC system monthly.
Microsoft Learn
- Records Management overview: https://learn.microsoft.com/purview/records-management
- Records vs regulatory records: https://learn.microsoft.com/purview/get-started-with-records-management
- File plan: https://learn.microsoft.com/purview/file-plan-manager
- Event-based retention: https://learn.microsoft.com/purview/event-driven-retention
- Auto-apply policies: https://learn.microsoft.com/purview/apply-retention-labels-automatically
- Disposition: https://learn.microsoft.com/purview/disposition
- Disposition reviewers: https://learn.microsoft.com/purview/disposition#stages-of-disposition
- Compliance role groups: https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions
- Licensing: https://learn.microsoft.com/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance
© vinayaklatthe, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/purview-records-management of vinayaklatthe/microsoft-security-skills.
Open the folder on GitHubat commit 15f16df
Compare with similar skills
Purview Records Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Purview Records Management this skillvinayaklatthe/microsoft-security-skills | 175 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Msgraphcodemie-ai/codemie-code | 294 | — | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| aai-cli Microsoft 365aai-labs/agent-barn | 109 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Workiqmicrosoft/work-iq | 1k | — | ~15k | Automated safety check: Pass | Custom licence | |
| Workiq Previewmicrosoft/work-iq | 1k | — | ~3.3k | Automated safety check: Pass | Custom licence | |
| Implementing Data Loss Prevention With Microsoft Purviewmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~7.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
aai-cli Microsoft 365
aai-labs/agent-barn
Guides work with Outlook, OneDrive, SharePoint, Teams, Excel, To Do and Planner through aai-cli's Microsoft Graph commands, starting from which service owns the data.
- Official
Workiq
microsoft/work-iq
WorkIQ tools for Microsoft 365 workplace data and actions. An agent skill from microsoft/work-iq.
- Official
Workiq Preview
microsoft/work-iq
WorkIQ tools for Microsoft 365 workplace data and actions. An agent skill from microsoft/work-iq.
Implementing Data Loss Prevention With Microsoft Purview
mukul975/Anthropic-Cybersecurity-Skills
Implements DLP policies using Microsoft Purview PowerShell cmdlets and the Graph API to protect data across Exchange Online, SharePoint, OneDrive, Teams, endpoints, and Power BI, including…
Sync Blocker Auditor
pnp/sharepoint-skills
Audits a SharePoint document library for names and paths that break OneDrive sync, File Explorer, and Teams file access.
More from vinayaklatthe/microsoft-security-skills
All 50 skills in this repoAPI Security Design
vinayaklatthe/microsoft-security-skills
Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API…
Azure App Service Security
vinayaklatthe/microsoft-security-skills
Guidance for securing Azure App Service web apps and APIs — managed identity, Easy Auth with Microsoft Entra ID, network isolation via private endpoints + VNet integration, HTTPS / TLS hardening…
Azure Arc
vinayaklatthe/microsoft-security-skills
Guidance for Azure Arc — projecting on-premises, multicloud (AWS/GCP), and edge servers, Kubernetes, and data services into Azure Resource Manager for unified governance, security, and management.
Azure Bastion Jit
vinayaklatthe/microsoft-security-skills
Guidance for secure remote VM management in Azure using Azure Bastion combined with Defender for Cloud just-in-time (JIT) VM access.
Azure Confidential Computing
vinayaklatthe/microsoft-security-skills
Guidance for Azure Confidential Computing — protecting data in use through hardware-based Trusted Execution Environments (TEEs).
Azure Ddos Protection
vinayaklatthe/microsoft-security-skills
Guidance for Azure DDoS Protection — Network Protection (per-VNet) and IP Protection (per public IP) tiers built on the same always-on Microsoft platform.
Related
Categories
Questions about Purview Records Management
What does Purview Records Management do?
Guidance for Microsoft Purview Records Management — declaring, managing, and disposing records across SharePoint, OneDrive, Exchange, and Teams. Purview Records Management is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for Microsoft Purview Records Management — declaring, managing, and disposing records across SharePoint, OneDrive, Exchange, and Teams.
When should I use Purview Records Management?
Purview Records Management fits situations like: non-records data lifecycle (use purview-data-lifecycle); DLP policies (use purview-dlp-policy); EDiscovery (use purview-ediscovery).
How do I install Purview Records Management in Claude Code?
Run `npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a claude-code`. Or copy the skill folder (skills/purview-records-management in vinayaklatthe/microsoft-security-skills) into .claude/skills/purview-records-management in your project. Claude Code loads it when a task matches its description.
How do I install Purview Records Management in Codex?
Run `npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a codex`. Or copy the skill folder (skills/purview-records-management in vinayaklatthe/microsoft-security-skills) into .agents/skills/purview-records-management in your project. Codex loads it when a task matches its description.
Can I use Purview Records Management in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vinayaklatthe/microsoft-security-skills --skill purview-records-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/purview-records-management, .gemini/skills/purview-records-management, .github/skills/purview-records-management and .opencode/skills/purview-records-management in your project.
What does Purview Records Management need to run?
SKILL.md names no scripts, command-line tools or credentials: Purview Records Management is instructions for the agent only.
Does Purview Records Management access the network?
SKILL.md names 1 domain. As links in the text: learn.microsoft.com. This is read from the text; nothing was executed.
Is Purview Records Management safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Purview Records Management use?
Purview Records Management is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Purview Records Management use?
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Purview Records Management?
Skills that share tags, products or a category with Purview Records Management: Msgraph (codemie-ai/codemie-code, 294 stars), aai-cli Microsoft 365 (aai-labs/agent-barn, 109 stars), Workiq (microsoft/work-iq, 1k stars) and Workiq Preview (microsoft/work-iq, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Purview Records Management?
vinayaklatthe (a GitHub user) maintains it in vinayaklatthe/microsoft-security-skills, which has 175 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on June 18, 2026.
Source: vinayaklatthe/microsoft-security-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.