compliant-phase

Enrich entity information via internal lookup before external web search.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/starlink-awaken/omostation-gbrain --skill compliant-phase-starlink-awaken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compliant-phase
Source: https://github.com/starlink-awaken/omostation-gbrain/tree/main/test/fixtures/brain-first-skills/compliant-phase
Command: npx skills add https://github.com/starlink-awaken/omostation-gbrain --skill compliant-phase-starlink-awaken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of redundant external API calls by enforcing a structured, brain-first verification process before searching the web.

Core Features & Use Cases

  • Brain-First Lookup: Prioritizes internal knowledge retrieval to minimize latency and external dependency.
  • External Enrichment: Seamlessly transitions to web search and citation cross-referencing only when internal data is insufficient.
  • Use Case: Use this when you need to verify technical entities or concepts, ensuring you leverage existing context before performing a live web search.

Quick Start

Use the compliant-phase skill to enrich the entity information for the provided subject by first checking internal knowledge and then searching the web.

Frequently Asked Questions about compliant-phase

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

FAQPage Schema
How do I verify entity information using internal knowledge before searching the web?

Entity verification uses a brain-first lookup process that checks internal context first, proceeding to external web search only when internal data is insufficient. This minimizes latency and redundant API calls during data enrichment.

What is brain-first entity enrichment and lookup?

Brain-first entity enrichment prioritizes internal context retrieval to resolve technical entities and concepts. It transitions to external web search only when existing knowledge is insufficient, ensuring accurate and verifiable output for research tasks.

How do I reduce redundant external API calls during data verification?

Reduce redundant external API calls by enforcing a structured two-phase verification process that leverages internal context first. This brain-first approach prevents unnecessary live web searches when internal knowledge already contains the answer.

Do I need web search and citation services to use this entity lookup process?

Yes, web search and citation service integrations are required. They enable the external enrichment phase to cross-reference data and ensure accurate, verifiable output when internal knowledge is insufficient for the lookup.

When should I use a two-phase entity lookup instead of direct web search?

Use a two-phase entity lookup for research and data verification tasks where minimizing external API usage is prioritized. It is ideal when you have existing internal context to leverage before performing a live web search.