initialize-machine

Configure machine authentication and hooks for AI Session Tracker.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/aef123/copilot-tracker --skill initialize-machine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: initialize-machine
Source: https://github.com/aef123/copilot-tracker/tree/main/plugins/copilot-session-tracker/skills/initialize-machine
Command: npx skills add https://github.com/aef123/copilot-tracker --skill initialize-machine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill configures the current machine for hooks-based AI Session Tracker. It installs hook scripts, configures authentication (certificate or Azure CLI), generates hooks configuration for Claude Code or Copilot CLI, and verifies connectivity.

Core Features & Use Cases

  • Configure authentication modes (certificate or Azure CLI) to obtain tokens without manual prompts.
  • Install and wire up hook scripts that trigger tracker events from Claude Code or Copilot CLI.
  • Generate and merge per-tool hook configurations (Claude Code: settings.json; Copilot CLI: hooks.json) with safe, idempotent merging.
  • Validate connectivity and token acquisition to ensure a reliable onboarding process.

Quick Start

Run the initialize-machine skill and follow the prompts to provide the tracker server URL, tenant ID, and resource ID to complete the setup.

Frequently Asked Questions about initialize-machine

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

FAQPage Schema
How do I configure Claude Code hooks for AI session tracking?

To configure Claude Code hooks for AI session tracking, you need to install hook scripts and merge per-tool hook configurations into settings.json, a process this setup automates safely and idempotently.

Does Claude Code session tracker setup work with Azure CLI authentication?

Yes, Claude Code session tracker setup works with Azure CLI authentication. It supports both certificate-based and Azure CLI user authentication to obtain tokens automatically without manual prompts.

How do I automate machine onboarding for Copilot CLI hooks?

You automate machine onboarding for Copilot CLI hooks by configuring authentication, generating hooks.json files, and validating connectivity against a specified tracker server URL, tenant ID, and resource ID.

What inputs are required to initialize hook scripts for session tracking on Windows?

To initialize hook scripts for session tracking on Windows, you must provide three mandatory inputs: the tracker server URL, tenant ID, and resource ID to complete the configuration safely.

Can I re-run machine setup for hook scripts without breaking existing configurations?

Yes, you can re-run machine setup for hook scripts without breaking existing configurations. The process performs idempotent, safe configuration with atomic writes and multi-tenant awareness.

What is the best way to validate AI Session Tracker connectivity after installing hooks?

The best way to validate AI Session Tracker connectivity is to run an automated setup that checks token acquisition and verifies the connection to the tracker server after deploying hooks.