by-session

Initialize BY sessions by configuring the environment and running the first-run questionnaire.

104|10|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/001TMF/blatant-why --skill by-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: by-session
Source: https://github.com/001TMF/blatant-why/tree/main/templates/.claude/skills/by-session
Command: npx skills add https://github.com/001TMF/blatant-why --skill by-session

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Session initialization, environment discovery, and first-run configuration for BY projects. It ensures a consistent starting point for new sessions and canonical project setup.

Core Features & Use Cases

  • Session banner and startup checks: prints a branded header and validates the environment at session start.
  • First-run questionnaire: guides the user through compute provider, model profile, and campaign defaults, writing .by/config.json.
  • Environment discovery & validation: maintains an up-to-date snapshot of host resources and helps downstream skills consume a canonical configuration.
  • Resume readiness: detects in-progress campaigns and defers full resume to by-campaign-manager.

Quick Start

Open a BY project directory and run the interactive questionnaire to create the initial .by/config.json.

Frequently Asked Questions about by-session

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

FAQPage Schema
How do I initialize a project session with environment discovery and config validation?

To initialize a project session, run the first-run questionnaire to configure compute providers and model profiles, which creates and validates the canonical .by/config.json file against the schema in references/config-schema.md.

What is a session-init workflow for configuring campaign defaults?

A session-init workflow establishes a consistent starting point for new sessions by guiding you through a questionnaire to set campaign defaults, writing them to .by/config.json, and displaying a session banner with startup checks.

How do I validate config.json against a schema before starting a session?

You validate config.json by running validate_config.py from the scripts directory, which checks your configuration against the schema defined in references/config-schema.md to ensure environment readiness.

Can I use by-session to resume in-progress campaigns directly?

by-session detects in-progress campaigns during environment discovery but defers full resume functionality to by-campaign-manager, ensuring proper downstream session management.

Does the first-run questionnaire support compute provider and model profile selection?

Yes, the first-run questionnaire guides you through selecting compute providers, model profiles, and campaign defaults, writing these settings directly into the canonical .by/config.json file.

What are the limitations of environment discovery in a session initialization workflow?

Environment discovery maintains a host resource snapshot and validates configuration, but it does not execute campaigns directly; it only surfaces in-progress campaigns and prepares the canonical config for downstream skills.