Writing for Astra

Write instructions that supply the context, constraints and outcomes Astra needs, leaving implementation choices to its judgment. Preserve the author's intent and requirements; reduce scaffolding only when it adds no useful behavior.

Purpose and scope

State the job and when the instructions apply. A skill description should name its specific trigger, without listing adjacent domains or carrying the workflow. Global availability does not mean the skill should run on every task.

What belongs in the root

Keep purpose, shared constraints, decision boundaries, relevant pointers and completion conditions in the root. Put conditional procedures and examples in supporting files, with a pointer explaining when each applies. Split by actual need, not to meet a line-count target or hide future steps from the model.