make

Run Make targets through a guarded wrapper and capture output to build/build.out.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/drusifer/via --skill make-drusifer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make
Source: https://github.com/drusifer/via/tree/main/agents/skills/make
Command: npx skills add https://github.com/drusifer/via --skill make-drusifer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates running Make targets through a guarded wrapper to ensure build output is captured and not spilled to the context, while maintaining a simple invocation interface.

Core Features & Use Cases

  • Guarded execution: All targets route through mkf so logs are centralized in build/build.out.
  • Verbosity control: Use V flags to control live output during builds.
  • Safe invocation: Discourages bypassing the Makefile or direct script calls to preserve correct behavior across environments.

Quick Start

Run make <target> and use V flags to control verbosity; mkf will capture all output.

Frequently Asked Questions about make

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

FAQPage Schema
How do I capture Makefile build output to a log file?

To capture Makefile build output, route targets through the mkf wrapper. This safely automates execution and centralizes all build logs directly into build/build.out.

How do I control verbosity when running Make targets?

You can control verbosity when running Make targets by passing V flags to the mkf wrapper. This dictates the level of live output displayed during your builds.

Why should I use a wrapper to run Make instead of calling targets directly?

Using a wrapper to run Make ensures safe invocation and prevents output from spilling into the context. Direct script calls are discouraged to preserve correct behavior across environments.

Can I use this to run targets from any standard Makefile?

Yes, you can use this to run targets from any standard Makefile. It supports usage across projects by routing standard targets through the guarded mkf wrapper.

Where are build logs stored when automating Make targets?

Build logs are stored centrally in build/build.out. The mkf wrapper captures all output from your Make targets and writes it directly to this file.

What is the best way to prevent build output from cluttering my context?

The best way to prevent build output from cluttering your context is automating Make targets through a guarded wrapper. This captures the output safely and logs it to build/build.out.