builder-log

Create timestamped Markdown entries, project snapshots, and growth reflections.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/C0ldSmi1e/builder-log-skill --skill builder-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: builder-log
Source: https://github.com/C0ldSmi1e/builder-log-skill/tree/main
Command: npx skills add https://github.com/C0ldSmi1e/builder-log-skill --skill builder-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Logging complex engineering work often leads to scattered notes, inconsistent formats, and lost context. This skill guides you to capture moments, projects, and growth reflections in a consistent Markdown structure, so your work is easy to review later.

Core Features & Use Cases

  • Three modes (Entry, Project snapshot, Growth check) to document single moments, complete projects, or high-level growth reflections.
  • Uses bundled templates to structure content and writes final Markdown files to your current working directory.
  • Slug-based file naming, auto-detection of existing structures, and minimal friction to record and recall.

Quick Start

Start by describing what you built or want to reflect on, and the skill will guide you through the appropriate workflow.

Frequently Asked Questions about builder-log

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

FAQPage Schema
How do I create a consistent markdown journal for my engineering projects?

You can document engineering work using three structured markdown modes: timestamped entries for single moments, project snapshots for portfolios, and growth checks for reflections. The skill applies frontmatter-driven templates to ensure consistent formatting and writes files directly to your current working directory.

What's the best way to document a completed software project for a portfolio?

Use the project snapshot mode to document a completed software project for a portfolio. This mode structures full project details into a markdown file with frontmatter, generates a slug-based filename, and includes templated sections to capture portfolio-ready context.

How do I log timestamped engineering work entries locally without a database?

Log timestamped engineering work entries locally by using the entry mode, which writes structured markdown files directly to your current working directory. This approach requires no database, relying entirely on local file generation and slug-based naming for organization.

Can I analyze past engineering work and growth reflections across multiple log files?

Yes, you can analyze past engineering work and growth reflections across multiple log files using the growth check mode. This mode zooms out to review your existing entries and project snapshots, helping you identify patterns and high-level growth over time.

Does this markdown logging workflow require any external dependencies or setup?

No external dependencies or setup are required for this markdown logging workflow. The skill operates independently using bundled templates to generate files in your current working directory, automatically detecting existing structures to minimize friction.