Notelane

v2.0.0

Organize notes as a personal knowledge base with tagging and full-text search. Use when capturing notes, searching entries, building a knowledge base.

0· 158·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for bytesagain3/notelane.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Notelane" (bytesagain3/notelane) from ClawHub.
Skill page: https://clawhub.ai/bytesagain3/notelane
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install notelane

ClawHub CLI

Package manager switcher

npx clawhub@latest install notelane
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (local knowledge base, tagging, search) match the included script and SKILL.md. Required binaries/env vars are none and the operations (date, grep, sed, tail, wc, du, cat) are appropriate for the stated functionality.
Instruction Scope
Runtime instructions and the script only create and read files under the user's data directory (~/.local/share/notelane) and use standard Unix tools; there are no instructions to read unrelated system configuration, send data externally, or access credentials.
Install Mechanism
There is no install spec (SKILL.md is instruction-heavy), yet a runnable script (scripts/script.sh) is included. That's not harmful but is an inconsistency: the package doesn't say how the script gets installed into PATH or invoked. A user or integrator will need to decide how/where to place and execute the script.
Credentials
The skill requests no environment variables or credentials. The script uses HOME to build a per-user data directory, which is proportional to a local note tool.
Persistence & Privilege
always is false and the skill writes only to its own user-scoped data directory. It does not modify system-wide configuration or other skills. Autonomous invocation is allowed by platform default but does not increase privilege beyond writing user files.
Assessment
This skill appears to be a simple, local Bash CLI for note-taking that stores all data under ~/.local/share/notelane and does not reach outside your machine. Two things to consider before installing: (1) the bundle includes a script but no install instructions — decide where to place it and inspect the script before running, and (2) it will create and append to files in your home directory (history.log and per-command .log files), so if you have sensitive data don't store it there. If you want extra caution, open the script (scripts/script.sh) and review it yourself, or run it in a disposable account/container first.

Like a lobster shell, security has layers — review code before you run it.

latestvk978yv56tps9cey3fmffaxz46x834j7g
158downloads
0stars
1versions
Updated 1mo ago
v2.0.0
MIT-0

Notelane

Notelane v2.0.0 — a productivity toolkit for adding, planning, tracking, reviewing, and organizing notes from the command line. Features streaks, reminders, prioritization, tagging, timelines, weekly reviews, and full data export.

Commands

Run notelane <command> [args] to use. Each data command accepts optional input — with no arguments it shows recent entries; with arguments it records a new entry.

CommandDescription
add [input]Add a new note or entry
plan [input]Record or review planning notes
track [input]Track progress on goals or tasks
review [input]Log review notes and reflections
streak [input]Track daily streaks and consistency
remind [input]Set and review reminders
prioritize [input]Record prioritization decisions
archive [input]Archive old notes and entries
tag [input]Tag entries for organization
timeline [input]Build timeline entries for projects or events
report [input]Generate or record summary reports
weekly-review [input]Log weekly review notes and retrospectives
statsShow summary statistics across all entry types
export <fmt>Export all data (formats: json, csv, txt)
search <term>Full-text search across all log entries
recentShow the 20 most recent history entries
statusHealth check — version, data dir, entry count, disk usage
helpShow built-in help message
versionPrint version string (notelane v2.0.0)

Features

  • 18+ subcommands covering the full note-taking and productivity lifecycle
  • Productivity-focused — streaks, reminders, prioritization, weekly reviews built in
  • Local-first storage — all data in ~/.local/share/notelane/ as plain-text logs
  • Timestamped entries — every record includes YYYY-MM-DD HH:MM timestamps
  • Unified history loghistory.log tracks every action for auditability
  • Multi-format export — JSON, CSV, and plain-text export built in
  • Full-text search — grep-based search across all log files
  • Zero external dependencies — pure Bash, runs anywhere
  • Automatic data directory creation — no setup required

Data Storage

All data is stored in ~/.local/share/notelane/:

  • add.log, plan.log, track.log, review.log, streak.log, remind.log, prioritize.log, archive.log, tag.log, timeline.log, report.log, weekly-review.log — per-command entry logs
  • history.log — unified audit trail of all operations
  • export.json, export.csv, export.txt — generated export files

Each entry is stored as YYYY-MM-DD HH:MM|<value> (pipe-delimited).

Requirements

  • Bash 4.0+ (uses set -euo pipefail)
  • Standard Unix utilities: date, wc, du, tail, grep, sed, cat, basename
  • No root privileges required
  • No internet connection required

When to Use

  1. Quick note capture — run notelane add "Meeting notes: decided to migrate to Postgres by Q3" to instantly record a thought or decision
  2. Planning and goal tracking — use notelane plan "Sprint 12: finish API refactor, deploy staging" and notelane track "API refactor 80% complete" to manage projects
  3. Building daily streaks — log daily habits with notelane streak "Day 15: morning workout done" to maintain consistency tracking
  4. Weekly retrospectives — use notelane weekly-review "Shipped 3 features, 1 bug regression, need more testing" to document weekly learnings
  5. Organizing with tags and timelines — tag entries with notelane tag "project:atlas priority:high" and build event timelines with notelane timeline "2024-03-15: v2.0 launched"

Examples

# Show all available commands
notelane help

# Add a quick note
notelane add "Idea: build a CLI dashboard for server metrics"

# Record a plan
notelane plan "This week: finalize docs, cut release, update changelog"

# Track progress
notelane track "Documentation: 3 of 5 sections complete"

# Log a reminder
notelane remind "Send invoice to client by Friday"

# Set priorities
notelane prioritize "P0: fix auth bug; P1: add export feature; P2: refactor tests"

# Run a weekly review
notelane weekly-review "Good week — shipped auth fix, started on export. Next: testing."

# View summary statistics
notelane stats

# Search all notes
notelane search "API"

# Export everything to JSON
notelane export json

# Check tool health
notelane status

How It Works

Notelane stores all data locally in ~/.local/share/notelane/. Each command logs activity with timestamps for full traceability. When called without arguments, data commands display their most recent 20 entries. When called with arguments, they append a new timestamped entry and update the unified history log.


Powered by BytesAgain | bytesagain.com | hello@bytesagain.com

Comments

Loading comments...