okhp3-sharepoint-content-auditor
OverKill Hill P³ · overkillhill.com · github.com/OKHP3
Use this skill to audit SharePoint UI screenshots captured during a manual list build. It turns screenshots into actionable build findings by comparing the visible UI settings against the repo's build cards, schema, and ADR decisions.
Host and evidence boundary
This is a portable, read-only SharePoint screenshot-review contract. The
copilot family is its catalog home; native Copilot in SharePoint discovery,
Agent Assets packaging, image inspection, and execution have not been verified.
Use a host that can inspect the supplied screenshots and reference documents.
If either input is inaccessible, report the missing evidence and request it
instead of inferring settings. No connector or live tenant access is required
or authorized. The rename preserves the existing list-build audit scope.
Scope
| In scope |
Out of scope |
| Screenshot review for list settings, column settings, indexes, views, and content types |
Making live SharePoint changes |
Matching UI evidence to schema/v2-build-cards.md |
Replacing human site-owner approval |
| Finding sticky-name, type, required, hidden, index, and delete-behavior issues |
Optical perfection or image cleanup |
Producing build corrections and v2-delta.md notes |
Full data migration validation |
Audit Workflow
- Inventory the screenshot folder. Preserve filename order and list every image reviewed.
- Read the matching build card from
schema/v2-build-cards.md.
- Read the matching field section from
schema/schema-fields.md if the card is ambiguous.
- Read the beachhead CSV header for the list and confirm screenshots do not imply extra/missing columns.
- Inspect each screenshot visually. Pay attention to user arrows, brackets, circles, and highlighted options.
- For each visible setting, classify it as
matches build card, must fix before data load, should fix before broad use, acceptable deviation if logged, or needs another screenshot.
- Produce a concise findings table with screenshot filename, UI evidence, expected setting, actual setting, severity, and action.
- If the finding changes schema intent, recommend an ADR or
v2-delta.md note. If it only corrects execution, recommend a SharePoint UI fix.
Critical Platform Constraint — Choice Columns Cannot Be Indexed
Choice columns (single-select or multi-select) cannot be indexed in SharePoint Online. The Edit Index UI does not offer Choice columns in the Primary Column dropdown. Any build card or plan that lists a Choice column as a planned index is incorrect and must be corrected before build.
Indexable types: Single line of text, Number, Date and Time, Yes/No, Lookup, Person/Group, Managed Metadata.
Non-indexable types: Choice, Multiple lines of text, Hyperlink, Calculated, Currency.
Impact on auditing: When reviewing an Indexed Columns screenshot, do not flag the absence of a Choice column as a missing index. Flag it as a build card correction required. If the builder created an index on an alternative non-Choice column instead, evaluate whether that substitution is documented and intentional.
What To Check
For list-level screenshots:
- URL and display name;
- description;
- content type management;
- attachments;
- comments;
- folders;
- search visibility;
- offline sync;
- Quick Edit;
- automatic index management;
- default view and mobile default view;
- indexed columns.
For column screenshots:
- display name and inferred internal name;
- final column type;
- required flag;
- unique values flag;
- max length or decimal places;
- default value;
- choice values;
- single-choice vs multi-choice display mode;
- fill-in choices;
- multi-line plain/rich/enhanced text;
- append changes;
- hidden status from content type page where available;
- index status where visible.
Severity Rules
| Severity |
Use when |
P0 stop build |
Sticky URL/internal name is wrong, wrong list created, or wrong column exists that would require rebuild. |
P1 fix before data load |
Column type, multi-choice vs single-choice, required setting, lookup behavior, index, or attachment setting conflicts with schema. |
P2 fix before broad use |
Governance setting weakens reliability but does not corrupt data immediately, such as Quick Edit or offline sync. |
P3 document |
Acceptable deviation, empty descriptions, or useful extra index that should be logged. |
ReferenceValues Confirmed Findings (2026-06-30 Screenshot Review)
From the analysis/artifacts/build-screenshots/01_ReferenceValues/ set reviewed in session sp-build-findings.md:
| Screenshot |
Finding |
Severity |
Action |
ReferenceGroup.png |
Display choices using = Checkboxes (multi-select). Expected: Drop-Down Menu (single-select). |
P1 fix before data load |
Edit Column → Display choices using: Drop-Down Menu; Fill-in: No |
SourceSystem.png |
Display choices using = Checkboxes (multi-select). Expected: Drop-Down Menu. |
P1 fix before data load |
Edit Column → Display choices using: Drop-Down Menu; Fill-in: No |
SortOrder.png |
Number of decimal places = Automatic. Expected: 0. |
P1 fix before data load |
Edit Column → Decimal places: 0 |
ValueLabel.png |
Description field empty. Max chars = 255 (correct for Single line of text). |
P3 document |
Add description text to column |
Definition.png |
Text type = Plain text (correct). Description empty. |
P3 document |
Add description text |
MapsFromValues.png |
Text type = Plain text (correct). Description empty. |
P3 document |
Add description text |
adv-01.png |
Attachments = Enabled. Expected: Disabled. |
P1 fix before data load |
List Settings → Advanced Settings → Attachments: Disabled |
adv-02.png |
Automatic Index Management = Yes. Expected: No for lists with manual index plan. |
P1 fix before data load |
List Settings → Advanced Settings → AIM: No |
indexes.png |
Index being created on Reference Code (Single line of text). Build card listed ReferenceGroup as an index — but ReferenceGroup is a Choice column and cannot be indexed. The builder discovered this at build time. ReferenceCode is a valid substitute. IsActive should also be indexed. |
Build card correction required |
Remove ReferenceGroup from Card 01 index list; add ReferenceCode as deliberate index substitute; confirm IsActive is indexed |
content-type.png |
Content type management appears enabled. Single content type "Item" present. IsActive shows Optional. |
P3 document |
IsActive is required per build card — verify required setting is confirmed in Edit Column, not only in content type view |
Reference Loading
Read references/shot-review.md when reviewing a new screenshot folder or when the user asks for image-by-image findings.
About
Built by Jamie Hill · OverKill Hill P³
Published at github.com/OKHP3
Part of the OKHP3/skillz Agent Skill library.
MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.
1---2name: okhp3-sharepoint-content-auditor3description: >4 OverKill Hill P³ SharePoint List build screenshot auditor.5 Use when reviewing screenshots of SharePoint Online list settings, column6 settings, indexed columns, content types, views, or Advanced Settings against7 a repo schema, build card, runbook, ADR, or CSV header. Also activate when the8 user says they captured SharePoint build screenshots, asks whether a list or9 column was configured correctly, points to arrows/markups in images, or needs10 a defect list before continuing manual SharePoint build work. This is the11 authoritative screenshot-review skill for this repo's UI-only SharePoint12 build process.13license: MIT14metadata:15 source: https://skillmd.com/skills/okhp3/okhp3-sharepoint-content-auditor16 author: Jamie Hill (OverKill Hill P³)17 version: "1.1.0"18 category: copilot19 target-host: sharepoint20 host-support: not-verified21 origin: okhp3/skillz22 homepage: https://overkillhill.com23 author-github: https://github.com/OKHP324 in_scope:25 - Review SharePoint list and column settings screenshots26 - Compare screenshots against build cards, schema fields, and CSV headers27 - Interpret user arrows, highlights, and markups in UI screenshots28 - Produce fix-before-load and log-as-deviation findings29 out_of_scope:30 - Direct SharePoint changes31 - Image editing or redrawing screenshots32 - Automated browser control of a live SharePoint tenant33---3435# okhp3-sharepoint-content-auditor3637**OverKill Hill P³** · [overkillhill.com](https://overkillhill.com) · [github.com/OKHP3](https://github.com/OKHP3)3839Use this skill to audit SharePoint UI screenshots captured during a manual list build. It turns screenshots into actionable build findings by comparing the visible UI settings against the repo's build cards, schema, and ADR decisions.4041## Host and evidence boundary4243This is a portable, read-only SharePoint screenshot-review contract. The44`copilot` family is its catalog home; native Copilot in SharePoint discovery,45Agent Assets packaging, image inspection, and execution have not been verified.46Use a host that can inspect the supplied screenshots and reference documents.47If either input is inaccessible, report the missing evidence and request it48instead of inferring settings. No connector or live tenant access is required49or authorized. The rename preserves the existing list-build audit scope.5051---5253## Scope5455| In scope | Out of scope |56|----------|-------------|57| Screenshot review for list settings, column settings, indexes, views, and content types | Making live SharePoint changes |58| Matching UI evidence to `schema/v2-build-cards.md` | Replacing human site-owner approval |59| Finding sticky-name, type, required, hidden, index, and delete-behavior issues | Optical perfection or image cleanup |60| Producing build corrections and `v2-delta.md` notes | Full data migration validation |6162---6364## Audit Workflow65661. Inventory the screenshot folder. Preserve filename order and list every image reviewed.672. Read the matching build card from `schema/v2-build-cards.md`.683. Read the matching field section from `schema/schema-fields.md` if the card is ambiguous.694. Read the beachhead CSV header for the list and confirm screenshots do not imply extra/missing columns.705. Inspect each screenshot visually. Pay attention to user arrows, brackets, circles, and highlighted options.716. For each visible setting, classify it as `matches build card`, `must fix before data load`, `should fix before broad use`, `acceptable deviation if logged`, or `needs another screenshot`.727. Produce a concise findings table with screenshot filename, UI evidence, expected setting, actual setting, severity, and action.738. If the finding changes schema intent, recommend an ADR or `v2-delta.md` note. If it only corrects execution, recommend a SharePoint UI fix.7475---7677## Critical Platform Constraint — Choice Columns Cannot Be Indexed7879**Choice columns (single-select or multi-select) cannot be indexed in SharePoint Online.** The Edit Index UI does not offer Choice columns in the Primary Column dropdown. Any build card or plan that lists a Choice column as a planned index is incorrect and must be corrected before build.8081**Indexable types:** Single line of text, Number, Date and Time, Yes/No, Lookup, Person/Group, Managed Metadata.82**Non-indexable types:** Choice, Multiple lines of text, Hyperlink, Calculated, Currency.8384**Impact on auditing:** When reviewing an Indexed Columns screenshot, do not flag the absence of a Choice column as a missing index. Flag it as a build card correction required. If the builder created an index on an alternative non-Choice column instead, evaluate whether that substitution is documented and intentional.8586---8788## What To Check8990For list-level screenshots:9192- URL and display name;93- description;94- content type management;95- attachments;96- comments;97- folders;98- search visibility;99- offline sync;100- Quick Edit;101- automatic index management;102- default view and mobile default view;103- indexed columns.104105For column screenshots:106107- display name and inferred internal name;108- final column type;109- required flag;110- unique values flag;111- max length or decimal places;112- default value;113- choice values;114- single-choice vs multi-choice display mode;115- fill-in choices;116- multi-line plain/rich/enhanced text;117- append changes;118- hidden status from content type page where available;119- index status where visible.120121---122123## Severity Rules124125| Severity | Use when |126|---|---|127| `P0 stop build` | Sticky URL/internal name is wrong, wrong list created, or wrong column exists that would require rebuild. |128| `P1 fix before data load` | Column type, multi-choice vs single-choice, required setting, lookup behavior, index, or attachment setting conflicts with schema. |129| `P2 fix before broad use` | Governance setting weakens reliability but does not corrupt data immediately, such as Quick Edit or offline sync. |130| `P3 document` | Acceptable deviation, empty descriptions, or useful extra index that should be logged. |131132---133134## ReferenceValues Confirmed Findings (2026-06-30 Screenshot Review)135136From the `analysis/artifacts/build-screenshots/01_ReferenceValues/` set reviewed in session `sp-build-findings.md`:137138| Screenshot | Finding | Severity | Action |139|---|---|---|---|140| `ReferenceGroup.png` | Display choices using = **Checkboxes** (multi-select). Expected: Drop-Down Menu (single-select). | P1 fix before data load | Edit Column → Display choices using: Drop-Down Menu; Fill-in: No |141| `SourceSystem.png` | Display choices using = **Checkboxes** (multi-select). Expected: Drop-Down Menu. | P1 fix before data load | Edit Column → Display choices using: Drop-Down Menu; Fill-in: No |142| `SortOrder.png` | Number of decimal places = **Automatic**. Expected: 0. | P1 fix before data load | Edit Column → Decimal places: 0 |143| `ValueLabel.png` | Description field empty. Max chars = 255 (correct for Single line of text). | P3 document | Add description text to column |144| `Definition.png` | Text type = Plain text (correct). Description empty. | P3 document | Add description text |145| `MapsFromValues.png` | Text type = Plain text (correct). Description empty. | P3 document | Add description text |146| `adv-01.png` | Attachments = **Enabled**. Expected: Disabled. | P1 fix before data load | List Settings → Advanced Settings → Attachments: Disabled |147| `adv-02.png` | Automatic Index Management = **Yes**. Expected: No for lists with manual index plan. | P1 fix before data load | List Settings → Advanced Settings → AIM: No |148| `indexes.png` | Index being created on `Reference Code` (Single line of text). Build card listed `ReferenceGroup` as an index — but **ReferenceGroup is a Choice column and cannot be indexed**. The builder discovered this at build time. `ReferenceCode` is a valid substitute. `IsActive` should also be indexed. | Build card correction required | Remove `ReferenceGroup` from Card 01 index list; add `ReferenceCode` as deliberate index substitute; confirm `IsActive` is indexed |149| `content-type.png` | Content type management appears enabled. Single content type "Item" present. `IsActive` shows Optional. | P3 document | IsActive is required per build card — verify required setting is confirmed in Edit Column, not only in content type view |150151---152153## Reference Loading154155Read `references/shot-review.md` when reviewing a new screenshot folder or when the user asks for image-by-image findings.156157---158159## About160161Built by [Jamie Hill](https://overkillhill.com) · [OverKill Hill P³](https://overkillhill.com)162Published at [github.com/OKHP3](https://github.com/OKHP3)163Part of the [OKHP3/skillz](https://github.com/OKHP3/skillz) Agent Skill library.164MIT License -- free to use, fork, and adapt. A nod to the source is appreciated.