Menu

Individual skill

init

Set up atk in a project: read the repository to find the build, test, and lint commands, the layer layout, the tracker, and the docs root, confirm what was found, ask only for what no file can answer, and write the profile every other skill reads. Use once when a team first installs atk in a project, and again when the project has moved on from what the profile says. Triggers on: "init", "atk init", "setup atk", "khởi tạo", "cấu hình dự án", "thiết lập atk", "初期設定", "セットアップ", "プロジェクト設定", "get atk working here", "/atk:init".

plugins/atk/skills/init/SKILL.md

Read pinned source

Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Project Setup (`atk:init`)

Writes `.atk/profile.md`, the file that tells every other skill how this project builds, where its
documents live, and who approves what. It is the first thing to run after installing the kit, and
the reason the other skills can stop guessing.

Most of the profile is already on disk. This skill reads it rather than asking, because a setup
interview that asks what `package.json` already says teaches the team that the kit does not read
their repository.

## Scope

Handles: resolving the project root and whether the project is one repository or several; detecting
project facts from manifests, lock files, CI workflows, and the git remote;