no-external

Rename the active log file with a .log.1 suffix and truncate it locally.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/weiping/gbrain-cn --skill no-external
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-external
Source: https://github.com/weiping/gbrain-cn/tree/main/test/fixtures/brain-first-skills/no-external
Command: npx skills add https://github.com/weiping/gbrain-cn --skill no-external

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents local log files from growing too large by rotating them on demand, keeping your system’s logging manageable without requiring any external services.

Core Features & Use Cases

  • Local-only log rotation: Renames the active log file and truncates it locally so logging can continue cleanly.
  • No external dependencies or queries: Operates purely on local state, with no brain queries and no external API calls.
  • Use Case: When you notice a log file getting too big during an ongoing run, you can rotate it immediately to manage storage and readability.

Quick Start

Ask an agent to rotate the local log file using the no-external skill.

Frequently Asked Questions about no-external

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

FAQPage Schema
How do I rotate a local log file without external API calls?

Local log file rotation renames the active log file with a .log.1 suffix and truncates the original file. This approach operates purely on local state without external dependencies or API calls.

What is local log rotation and when do I need it?

Local log rotation prevents uncontrolled log growth by renaming and truncating active log files. You need it when local operations grow too large during an ongoing run and require immediate management for storage and readability.

Can I truncate an active log file without stopping my running process?

Yes, you can truncate an active log file during an ongoing run by renaming it locally with a .log.1 suffix and clearing the original file, allowing logging to continue cleanly without external services.

Do I need any external dependencies or queries to manage local log file growth?

No, managing local log file growth does not require external dependencies or brain queries. Local log rotation operates entirely on local state by reading the log path from configuration and truncating the active file.

What is the best way to keep local logging manageable without external services?

The best way to keep local logging manageable without external services is on-demand local log rotation, which renames the active log file and truncates it locally to prevent uncontrolled local log growth.