research-schema-scrape

Recover the data model behind an existing product from its interface, exports, and documentation.

1|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Lia-Creative/lia-plugins --skill research-schema-scrape-lia-creative
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-schema-scrape
Source: https://github.com/Lia-Creative/lia-plugins/tree/main/lia-tools/skills/research-schema-scrape
Command: npx skills add https://github.com/Lia-Creative/lia-plugins --skill research-schema-scrape-lia-creative

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When researching a competitor or reference product, teams often guess at the underlying data model from surface impressions. This Skill provides a disciplined method for reconstructing the entities, fields, relationships, and enforced rules of an existing product, with every claim evidenced by the screen, export, or endpoint it was read from. ## Core Features & Use Cases - Entity and field recovery: Identify the nouns a product is built on, each field's name, type, required status, constraints, and the label the product shows for it. - Evidence-first sourcing: Prefer documented models (API references, schema endpoints, export files, import templates) over interface inference, and mark every line as documented or inferred. - Relationship and rule mapping: Capture cardinality, cascade behavior on deletion, validation, uniqueness, ordering, permissions, and derived-versus-stored fields. - Use Case: Researching Folk CRM's person record — walk the product, pull the CSV import template, capture the forms with ui-capture, and produce a per-entity field table with locators for every claim. ## Quick Start Ask the agent to research the schema domain of a specific product, for example: scrape the schema from Folk CRM and document the person entity's fields, relationships, and enforced rules.

Frequently Asked Questions about research-schema-scrape

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reverse-engineer a product's data model?▼

Start with documented sources like API references, schema endpoints, export files, and CSV import templates, which state the model directly. Where only the interface is available, capture forms and detail views as evidence, and mark every field as documented or inferred.

What is the best evidence for a product's schema during competitive research?▼

Export files and import templates are the strongest evidence and are routinely overlooked — a CSV template names the fields, their order, and the required set. Official API documentation and captured interface screens with dates also qualify.

Can I test field constraints in another company's product?▼

Only where you legitimately can: in your own account, on your own data, and within the product's terms of service. Never scrape at scale, touch another person's data, or bypass access control — untestable constraints are recorded as inferred.

How do I tell derived fields from stored fields when analyzing a product?▼

A computed field read as a stored one is the classic error in schema research. Cross-check the interface against exports and API responses — if a value appears only in views but never in exports or write endpoints, it is likely derived.

What are the limitations of interface-only schema research?▼

A model read only through the interface is honest and useful but not a specification — it should be marked DEVELOPING. Features gated behind account tiers or permissions you lack become documented Gaps rather than guesses.