grilo_falante

Classify content by epistemic strength using GMIF levels and persist claims in PostgreSQL with pgvector.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/rodolfomatos/grilo-falante --skill grilo-falante
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grilo_falante
Source: https://github.com/rodolfomatos/grilo-falante/tree/main
Command: npx skills add https://github.com/rodolfomatos/grilo-falante --skill grilo-falante

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Grilo Falante skill provides a lightweight workflow to analyze content by applying GMIF classification, persist results across sessions in PostgreSQL with pgvector, and assign GF-IDs for traceable governance.

Core Features & Use Cases

  • GMIF classification: automatically label claims with M1–M7 strength.
  • Persistent memory: stores results in PostgreSQL to enable cross-session retrieval and auditability.
  • GF-IDs: generates stable identifiers for claims to support provenance and linking.
  • Use Case: analysts can extract epistemic structure from code or documents and track how evidence evolves across sessions.

Quick Start

Load the regime with grilo_load() and grilo_acordar(temporal_anchor="YYYY-MM-DD", intention="...") and then feed content to the grilo_falante skill to analyze and persist GMIF-classified claims with GF-IDs.

Frequently Asked Questions about grilo_falante

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

FAQPage Schema
How do I classify and persist epistemic claims in PostgreSQL for cross-session auditing?

To classify and persist epistemic claims in PostgreSQL, you can use this Skill to apply GMIF levels (M1-M7) to content, store results with pgvector support, and assign stable GF-IDs for cross-session traceability and rollback.

What is GMIF classification and how does it track claim provenance?

GMIF classification is a method of labeling content by epistemic strength using levels M1 through M7. It tracks claim provenance by assigning GF-IDs, enabling structured auditing and cross-session evidence evolution tracking.

How do I analyze documents with GMIF levels and store results in a PostgreSQL database?

You analyze documents by loading the regime with grilo_load() and grilo_acordar(), then feeding content to the Skill. It automatically labels claims with GMIF strength and persists them in PostgreSQL for retrieval.

Does pgvector support vector search for epistemic governance and claim retrieval?

Yes, pgvector supports vector search for epistemic governance by enabling cross-session retrieval of GMIF-classified claims. This allows analysts to query persisted evidence and track context evolution within the database.

Can I use persistent memory to audit GMIF distributions across multiple sessions?

Yes, you can audit GMIF distributions across multiple sessions because the Skill persists claims, context, and GF-IDs in PostgreSQL. This cross-session memory outputs a structured representation suitable for auditing and rollback.

What are the limitations of using GF-IDs and PostgreSQL for epistemic governance?

The primary constraint is the dependency on PostgreSQL with pgvector for persistent memory. Without this database environment configured, the Skill cannot store GMIF distributions, assign GF-IDs, or support cross-session traceability.