OpenParable
Skip to content
← Back to skills

Profile Test Skill

Testing & Quality
profile-test-skill

Profile Test Skill is an Agent Skill for testing & quality published in the microsoft/waza repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

**PROFILE TEST** - A skill for testing the profile command. USE FOR: testing profile analysis, verifying structural metrics. DO NOT USE FOR: production use.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/microsoft/waza/blob/HEAD/cmd/waza/tokens/testdata/profile/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/profile-test-skill, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Profile Test Skill

A test skill used for verifying the waza tokens profile command.

Activation Triggers

Use this skill when:

  • Running profile analysis tests
  • Verifying section counting
  • Checking code block detection

Workflow

  1. Parse the file - Read SKILL.md and extract frontmatter
  2. Analyze structure - Count sections, code blocks, steps
  3. Generate summary - Produce one-line profile output
  4. Check warnings - Flag potential issues

Code Examples

Example 1: Basic Usage

waza tokens profile my-skill

Example 2: JSON Output

{
  "name": "my-skill",
  "tokens": 500,
  "sections": 5
}

Example 3: Table Output

File          Tokens   Sections
-------------------------------
SKILL.md         500          5

Configuration

Set up your skill with proper frontmatter:

name: my-skill
description: A useful skill

Guidelines

  • Keep token count under 2500
  • Include workflow steps
  • Use clear section headings