Loading the registry…
Expert at Microsoft Graph API integration for SharePoint and Microsoft 365 — authenticating an app and driving the site-id → list-id → item request chain over REST. Use this skill whenever the user wants to read or write SharePoint list items via Graph, set up an Entra ID app registration, choose delegated vs application permissions and scopes, acquire tokens (authorization code, client credentials, on-behalf-of) with MSAL, page through large result sets, combine calls with $batch, handle 429 throttling, or call Graph from Power Automate or a Power Apps custom connector. Trigger on "call Microsoft Graph", "Graph API to read a SharePoint list", "app registration permissions", "Sites.ReadWrite.All", "Sites.Selected", "429 throttling", "$batch", "custom connector for Graph", "get site id", "expand=fields", "on-behalf-of flow". Implicit signals: a daemon/service that must touch SharePoint without a signed- in user, an integration that needs list data outside the app, a flow that hits a Graph URL, an OAuth token error against graph.microsoft.com. Boundaries: designing the list's columns/views/content-types is sharepoint-list- architecture; JSON column/view formatting is sharepoint-column-formatting; in-app data access from a canvas app (native SharePoint connector, delegation) is power-fx-development; pulling list data into Power BI reporting is power-query-m. This skill owns *Graph API usage*, not the list nor the app.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
67 critical findings reported by agent-audit-kit, 0 of them in the installed artifact. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- graph-api-integration
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- graph-api-integration ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
20 findings · 0.8s
v2.0.11
70 findings · 13.7s
v0.3.26
81 findings · 3.5s
v0.1.0
0 findings · 4.3s
v0.1.0
0 findings · 4.3s
v2.3.8
0 findings · 1.4s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.4s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
No report in this scan: nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 14, 2026 | Flagged80 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 171 findings above stand exactly as their scanners reported them, at full severity.