How do I install the Logifai skill?

Run npx skillmds@latest add tomevault-io/logifai in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Logifai safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Logifai?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Logifai free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Logifai?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Logifai by tomevault-io — Agent Skill

Name: Logifai
Author: tomevault-io

Logifai

Search and analyze development logs captured by logifai. Use when investigating errors, debugging runtime issues, or reviewing recent application activity. Triggered when user mentions "logs", "errors", "what went wrong", references recent failures, or pastes a logifai:// URI reference. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

logifai Development Logs

logifai automatically captures output from development commands (e.g. npm run dev 2>&1 | logifai) and saves them as NDJSON files.

Log Location

~/.local/state/logifai/logs/
├── session-YYYYMMDD-HHmmss-{id}.ndjson   # Session files
└── current.ndjson -> session-...ndjson     # Symlink to latest session

NDJSON Schema

Each line is a JSON object:

{
  "timestamp": "2026-02-08T10:30:45.123Z",
  "level": "ERROR | WARN | INFO | DEBUG",
  "message": "Log message text",
  "source": "npm-run-dev",
  "project": "/home/user/my-app",
  "session_id": "a1b2c3d4",
  "git_branch": "feature/auth",
  "git_commit": "e91d055",
  "pid": 12345,
  "raw": true,
  "stack": "Error stack trace if detected",
  "_original": {}
}

Quick Search Commands

List recent sessions

ls -lt ~/.local/state/logifai/logs/session-*.ndjson | head -10

Search current session for errors

grep '"level":"ERROR"' ~/.local/state/logifai/logs/current.ndjson

Search all sessions for a keyword

grep -l "keyword" ~/.local/state/logifai/logs/*.ndjson

Get context around an error

grep -B 5 -A 5 "Module not found" ~/.local/state/logifai/logs/current.ndjson

Find errors with stack traces

grep '"stack"' ~/.local/state/logifai/logs/current.ndjson | grep -v '"stack":null'

Advanced Queries (with jq)

# Last 50 ERROR entries
tail -n 500 ~/.local/state/logifai/logs/current.ndjson | jq 'select(.level == "ERROR")' | tail -50

# Errors after a specific time
jq 'select(.level == "ERROR" and .timestamp >= "2026-02-08T10:00:00")' ~/.local/state/logifai/logs/current.ndjson

# Errors with stack traces
jq 'select(.level == "ERROR" and .stack != null)' ~/.local/state/logifai/logs/current.ndjson

# Group by level
jq -s 'group_by(.level) | map({level: .[0].level, count: length})' ~/.local/state/logifai/logs/current.ndjson

Log Line References

Users may paste log line references from the Web UI in the format logifai://SESSION_ID:LINES.

Resolve a reference

logifai show 'logifai://a1b2c3d4:42,50-55'

When user pastes a logifai:// reference

Run logifai show '<reference>' to resolve it
Parse the JSON output to understand the log entries
Analyze as requested (explain errors, suggest fixes, etc.)

Reference format

Single line: logifai://a1b2c3d4:42
Multiple lines: logifai://a1b2c3d4:42,45,50
Range: logifai://a1b2c3d4:42-55
Mixed: logifai://a1b2c3d4:10,20-30,50
Multiple sessions: logifai://a1b2c3d4:10-15+ff990011:1-5

Investigation Workflow

When user asks about errors or issues:

Check current.ndjson for recent ERROR entries
Look for stack traces (.stack != null)
Check surrounding WARN/INFO entries for context
Search across sessions if not found in current

When user asks "what went wrong":

Search for ERROR level logs in current session
Check for stack traces
Look for related WARN logs nearby
Summarize findings with timestamps and context

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: logifaidescription: Search and analyze development logs captured by logifai. Use when investigating errors, debugging runtime issues, or reviewing recent application activity. Triggered when user mentions "logs", "errors", "what went wrong", references recent failures, or pastes a logifai:// URI reference. Use when this capability is needed.---# logifai Development Logslogifai automatically captures output from development commands (e.g. `npm run dev 2>&1 | logifai`) and saves them as NDJSON files.## Log Location```~/.local/state/logifai/logs/├── session-YYYYMMDD-HHmmss-{id}.ndjson # Session files└── current.ndjson -> session-...ndjson # Symlink to latest session```## NDJSON SchemaEach line is a JSON object:```json{ "timestamp": "2026-02-08T10:30:45.123Z", "level": "ERROR | WARN | INFO | DEBUG", "message": "Log message text", "source": "npm-run-dev", "project": "/home/user/my-app", "session_id": "a1b2c3d4", "git_branch": "feature/auth", "git_commit": "e91d055", "pid": 12345, "raw": true, "stack": "Error stack trace if detected", "_original": {}}```## Quick Search Commands### List recent sessions```bashls -lt ~/.local/state/logifai/logs/session-*.ndjson | head -10```### Search current session for errors```bashgrep '"level":"ERROR"' ~/.local/state/logifai/logs/current.ndjson```### Search all sessions for a keyword```bashgrep -l "keyword" ~/.local/state/logifai/logs/*.ndjson```### Get context around an error```bashgrep -B 5 -A 5 "Module not found" ~/.local/state/logifai/logs/current.ndjson```### Find errors with stack traces```bashgrep '"stack"' ~/.local/state/logifai/logs/current.ndjson | grep -v '"stack":null'```## Advanced Queries (with jq)```bash# Last 50 ERROR entriestail -n 500 ~/.local/state/logifai/logs/current.ndjson | jq 'select(.level == "ERROR")' | tail -50# Errors after a specific timejq 'select(.level == "ERROR" and .timestamp >= "2026-02-08T10:00:00")' ~/.local/state/logifai/logs/current.ndjson# Errors with stack tracesjq 'select(.level == "ERROR" and .stack != null)' ~/.local/state/logifai/logs/current.ndjson# Group by leveljq -s 'group_by(.level) | map({level: .[0].level, count: length})' ~/.local/state/logifai/logs/current.ndjson```## Log Line ReferencesUsers may paste log line references from the Web UI in the format `logifai://SESSION_ID:LINES`.### Resolve a reference```bashlogifai show 'logifai://a1b2c3d4:42,50-55'```### When user pastes a logifai:// reference1. Run `logifai show '<reference>'` to resolve it2. Parse the JSON output to understand the log entries3. Analyze as requested (explain errors, suggest fixes, etc.)### Reference format- Single line: `logifai://a1b2c3d4:42`- Multiple lines: `logifai://a1b2c3d4:42,45,50`- Range: `logifai://a1b2c3d4:42-55`- Mixed: `logifai://a1b2c3d4:10,20-30,50`- Multiple sessions: `logifai://a1b2c3d4:10-15+ff990011:1-5`## Investigation WorkflowWhen user asks about errors or issues:1. Check `current.ndjson` for recent ERROR entries2. Look for stack traces (`.stack != null`)3. Check surrounding WARN/INFO entries for context4. Search across sessions if not found in currentWhen user asks "what went wrong":1. Search for ERROR level logs in current session2. Check for stack traces3. Look for related WARN logs nearby4. Summarize findings with timestamps and context---> Converted and distributed by [TomeVault](https://tomevault.io/claim/tomoyaf) — claim your Tome and manage your conversions.

Frequently asked questions