lfx-research

Explore LFX repositories to validate API contracts and read architecture documents.

8|1|Updated Mar 16, 2026

Search Tags:#research #openapi #architecture-docs #codebase-exploration #structured-findings #upstream-api #goa-design

Ready to run

npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lfx-research
Source: https://github.com/linuxfoundation/lfx-skills/tree/main/lfx-research
Command: npx skills add https://github.com/linuxfoundation/lfx-skills --skill lfx-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read-only exploration agent for LFX repositories. Your job is to gather upstream API contracts, codebase patterns, architecture docs, and examples for the /lfx-coordinator to consume.

Core Features & Use Cases

Upstream API validation and OpenAPI exploration
Codebase discovery and pattern extraction
Architecture documentation reading and mapping
Example discovery and pattern extraction
Structured findings ready for /lfx-coordinator planning

Quick Start

Instruct the agent to perform a read-only analysis of the target repo and return structured findings for the coordinator.

Frequently Asked Questions about lfx-research

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

FAQPage Schema

How do I explore OpenAPI specs and architecture docs before generating code?▼

Read-only repository exploration validates upstream API contracts by detecting repo type, reading OpenAPI specs, Goa designs, and architecture docs to produce structured findings for downstream planning.

Can I extract codebase patterns from LFX repositories without modifying the code?▼

Yes, read-only codebase exploration discovers existing code patterns and examples across APIs, UI, and backend domains, returning concise structured findings without altering the repository.

What's the best way to validate upstream API contracts before writing new code?▼

Validating upstream API contracts is best done through read-only exploration that reads OpenAPI specs and Goa designs, mapping architecture documents to ensure planned code aligns with existing interfaces.

How do I prepare structured findings for a coordinator agent to consume?▼

You prepare structured findings by instructing the agent to perform a read-only analysis of the target repo, extracting API contracts and architecture patterns for the coordinator to consume.

Does this approach work with Goa design patterns and OpenAPI specifications?▼

Yes, the exploration specifically reads Goa designs and OpenAPI specifications to validate API contracts and extract codebase patterns for structured downstream consumption.

Are there limitations to read-only codebase exploration for code generation?▼

Read-only exploration is limited to analyzing existing repository structures, detecting repo types, and reading architecture docs, meaning it cannot modify code or execute dynamic runtime tests.