info-record

Record and deduplicate business intelligence items in a SQLite database.

8.4k|1.4k|Updated Apr 24, 2024
One-click install
npx skills add https://github.com/TeamWiseFlow/wiseflow --skill info-record
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: info-record
Source: https://github.com/TeamWiseFlow/wiseflow/tree/main/addons/officials/crew/business-developer/skills/info-record
Command: npx skills add https://github.com/TeamWiseFlow/wiseflow --skill info-record

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sqlite3, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of repeatedly collecting the same business-intel items during intel-gathering workflows, wasting time and increasing noise in your daily deliverables.

Core Features & Use Cases

  • Persistent SQLite intel ledger: Maintains a durable info_record.db at ./db/info_record.db to track already collected items.
  • Duplicate detection by source: Checks whether a given source (URL or platform-identifier) already exists before opening and collecting the details again.
  • Daily query for delivery preparation: Retrieves all records collected today for downstream reporting and output generation (e.g., compiling a “today’s intel” package).
  • Use case: When reviewing new posts/videos for a day’s intel-gathering task, you can skip items already stored from earlier runs, then record only the newly collected content and generate a clean daily list.

Quick Start

Ask the system to initialize the database by running: bash ./skills/info-record/scripts/init-db.sh.

Frequently Asked Questions about info-record

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

FAQPage Schema
How do I prevent duplicate business intelligence collection during daily reporting workflows?▼

You can prevent duplicate business intelligence collection by recording items in a persistent SQLite database. The system checks if a source URL already exists before collection and filters records by creation date for daily reporting.

How do I check if a source URL has already been captured in SQLite?▼

To check if a source URL has already been captured in SQLite, the system queries the `intel_items` table in `info_record.db`. It returns a JSON output indicating whether the given source exists before you open and collect the details again.

What is the best way to compile a daily intel report from collected business research?▼

The best way to compile a daily intel report is by querying the SQLite database for items collected today. The system filters records using the `created_at` timestamp and returns a JSON output of the day's gathered business research for your deliverables.

Do I need sqlite3 to record and deduplicate gathered intel items?▼

Yes, you need sqlite3 to record and deduplicate gathered intel items. The Skill depends on sqlite3 to maintain the `info_record.db` database file and insert rows into the `intel_items` table for persistent tracking.

How does JSON output work when querying today's collected intel items?▼

JSON output works by returning structured data from check, record, and query scripts against the SQLite database. When querying today's collected intel items, the system filters by the `created_at` date and outputs the results in JSON format for downstream integration.