_lib

Track per-skill usage counters and render canonical mode-line hints.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill lib
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _lib
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/skills/_lib
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill lib

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides the shared infrastructure that other skills rely on for consistent usage tracking, mode-line rendering, and discovery hints. It prevents each skill from reimplementing the same decay rules, counter storage, and fallback behavior.

Core Features & Use Cases

  • Usage Counter Management: Tracks how often each skill runs and when it was last used.
  • Mode-Line UX Support: Supplies the canonical mode-line spec and the helper logic behind flashy versus dim presentation.
  • Fail-Open Reliability: Keeps calling skills working even when optional tooling such as jq or platform-specific date parsing is unavailable.
  • Use Case: A planning, fix, qa, or implement skill can call this shared helper to decide whether to show a full ladder, a compact hint, or no hint at all.

Quick Start

Use the _lib skill as the shared helper layer whenever another skill needs usage counting or canonical mode-line guidance.

Frequently Asked Questions about _lib

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

FAQPage Schema
How do I add usage tracking and invocation counters to shared bash scripts?

Usage tracking in bash scripts requires shared helpers that record per-skill invocation counters and store last-used timestamps. This infrastructure enables decay-based hint rendering and consistent usage counting across multiple skills without duplicating counter logic.

What is fail-open bash logic for handling missing optional dependencies like jq?

Fail-open bash logic is a fallback design pattern that keeps calling scripts running even when optional dependencies like jq or platform-specific date commands are unavailable. It ensures core functionality continues by gracefully degrading instead of crashing when tooling is missing.

How do I implement decay-based hint rendering for command-line interfaces?

Decay-based hint rendering uses shared helpers that check a usage counter and last invocation timestamp to decide whether to display a full mode-line, a compact hint, or no hint. This prevents interface clutter by gradually fading out infrequently used guidance.

Does cross-platform date handling in bash work without external parsing tools?

Cross-platform date handling works without external parsing tools by using fail-open bash fallback logic. If platform-specific date parsing or jq is unavailable, the shared helpers ensure the calling skill keeps working by skipping non-critical operations gracefully.

Why do my bash helper scripts crash when jq is not installed on the system?

Bash scripts crash when jq is missing if they lack fail-open fallback logic. Using shared skill infrastructure with fail-open design ensures calling skills keep working even when optional dependencies like jq or platform-specific date handling are unavailable.

Can I use shared helpers to standardize mode-line UX across multiple command-line skills?

You can use shared helpers to standardize mode-line UX by providing a canonical mode-line spec and helper logic for flashy versus dim presentation. This ensures consistent visual rules across multiple skills without each script reimplementing its own presentation logic.