okhp3-sharepoint-list-schema-design
OverKill Hill P³ SharePoint List database architecture reviewer. Use when designing, reviewing, or hardening SharePoint Online Lists used as lightweight databases, controlled vocabularies, lookup-backed registries, or CMDB-lite data stores. Also activate when the user asks about list thresholds, indexed columns, lookup relationships, required fields, content types, attachments, offline sync, Quick Edit, SharePoint UI-only build constraints, or whether a SharePoint list setting is safe for database-like use. This is the authoritative SharePoint-list-as-database architecture skill for this repo -- use it even when the user only says "SharePoint list settings" or "list build".
Target: Design & content creation. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- okhp3-sharepoint-list-schema-design
- Host and evidence boundary
- Scope
- Review Workflow
- Platform Hard Limits
- Default Traps (Settings That Are Wrong Out of the Box)
- Column Type Decision Matrix
- Beachhead CSV Import Pattern
OverKill Hill P³ · overkillhill.com · github.com/OKHP3 Use this skill to review SharePoint Online Lists that are intentionally being used as governed, database-like structures. The goal is not to pretend SharePoint is a relational database. The goal is to keep a SharePoint UI-only build inside known limits while preserving governance, queryability, and migration sanity. This is a portable, draft-producing SharePoint list-design contract. The copilot family is its catalog home; native Copilot in SharePoint discovery, Agent Assets packaging, and execution have not been verified. Supply the schema, build cards, runbook, and applicable decisions to a host that can read them. If those inputs are unavailable, state the gap before proposing a design. The skill does not provision lists or change a tenant. Any later implementation requires a separately authorized workflow and the site's existing permissions. -- | In scope | Out of scope | |----------|-------------| | SharePoint Online Lists as controlled registries | SQL Server, Dataverse, ServiceNow, or full CMDB implementation | | List/column settings chosen through SharePoint UI | PowerShell, SPFx, PnP, Graph automation | | Indexing, loo
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- OKHP3/skillz
- Source file
- copilot/okhp3-sharepoint-list-schema-design/SKILL.md
- Fixed revision
- 7b187777d42ab7bc7bab1e5f2c940cd3139ecebf
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: OKHP3/skillz · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T10:00:54.718Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.