journal

Filter JSONL operation journal entries by date, skill, outcome, or signer.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/manifest-network/manifest-agent-plugin --skill journal-manifest-network
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: journal
Source: https://github.com/manifest-network/manifest-agent-plugin/tree/main/skills/journal
Command: npx skills add https://github.com/manifest-network/manifest-agent-plugin --skill journal-manifest-network

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a streamlined way to access and review the complete audit trail of state-changing skill invocations, ensuring transparency and accountability in system operations.

Core Features & Use Cases

  • Operation Journal Browsing: Browse the append-only logs stored in JSONL format, filtered by date, skill, outcome, signer, or lease UUID.
  • Filtered Queries: Enable precise searches such as recent failures, specific time ranges, or particular user actions, supporting troubleshooting and audit compliance.
  • Use Case: An administrator wants to verify all failed deployment attempts within the last week—this Skill allows querying the journal with those filters for quick insights.

Quick Start

Prompt the system to filter and retrieve journal entries for a specific date range or outcome to analyze system activity.

Frequently Asked Questions about journal

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

FAQPage Schema
How do I filter system activity logs by date and outcome for troubleshooting?

To filter system activity logs for troubleshooting, query the JSONL operation journal using criteria like date range, outcome, or signer to retrieve specific state-changing skill invocations and review failed or successful events.

What is the best way to audit failed skill invocations within a specific time range?

Auditing failed skill invocations requires querying the append-only operation journal logs with filters for outcome and date range, allowing administrators to isolate specific time windows and verify all deployment or execution failures quickly.

Can I search JSONL log entries by signer or lease UUID to track user actions?

Searching JSONL log entries by signer or lease UUID is fully supported, enabling precise tracking of individual user actions and specific system events within the plugin environment for audit compliance and accountability.

Does the journal Skill require external dependencies to process local JSONL operation logs?

The journal Skill requires no external dependencies to process local JSONL operation logs, functioning entirely within the plugin environment to retrieve and filter state-changing skill invocation records using scripts.

How to retrieve recent operation journal entries for a specific skill?

Retrieving recent operation journal entries for a specific skill involves applying a skill name filter to the JSONL logs, returning matching state-changing invocations sorted by date to analyze recent system activity and outcomes.

Why should I use an append-only operation journal instead of standard logging for audit compliance?

An append-only operation journal ensures transparency and accountability by maintaining an immutable audit trail of state-changing skill invocations, unlike standard logging which may be overwritten or altered during system troubleshooting and review.