// Create and update repo-local skills that follow the MetaMask Mobile standard. Use for new repo-local skills, skill entrypoints, or harness shims in this repository.
| name | repo-skill-authoring |
| description | Create and update repo-local skills that follow the MetaMask Mobile standard. Use for new repo-local skills, skill entrypoints, or harness shims in this repository. |
Canonical guidance for creating and updating repo-local skills in MetaMask Mobile.
Use this standard when the repo needs a reusable agent workflow with stable instructions, validation, or harness shims.
Do not create a skill when one of these is enough:
AGENTS.md or a narrow tests/AGENTS.md pointerdocs/Create a skill when the work is repeated, fragile, or benefits from a shared workflow across agents.
Use the native or harness-provided skill-creator guidance for general skill design principles or when creating a skill outside this repository.
Use repo-skill-authoring for any MetaMask Mobile repo-local skill that should live in .agents/skills/, .claude/, or other repo-owned harness folders.
If both apply, use native skill-creator for general design guidance, and use this skill as the source of truth for repository-specific structure, naming, and entrypoints.
Use these entrypoints:
.agents/skills/repo-skill-authoring/SKILL.md ($repo-skill-authoring).claude/skills/repo-skill-authoring/SKILL.mdRequired shape for a repo-local skill:
.agents/skills/<skill-name>/SKILL.md
.agents/skills/<skill-name>/agents/openai.yaml
Optional shape, when the workflow needs it:
.agents/skills/<skill-name>/scripts/
.agents/skills/<skill-name>/references/
.agents/skills/<skill-name>/assets/
.claude/skills/<skill-name>/SKILL.md
Keep .agents/skills/<name>/SKILL.md as the single source of truth. Any harness-specific shim should point directly to it.
SKILL.md frontmatter name must match exactly.description must say what the skill does and when to use it.For agent implementation and review tasks, follow this workflow:
SKILL.md.scripts/ only when deterministic validation or repeated logic is worth the maintenance cost.references/ only when detailed content should be loaded on demand instead of sitting in the skill body.name and description..claude/skills/<name>/SKILL.md when Claude needs a pointer..agents/skills/<name>/SKILL.md.Authoring principle:
Required agent response sections:
Implementation ChecklistFiles To Add Or ModifyValidationAssumptions---
name: topic
description: Create and update the repo-local topic workflow. Use for new skill content or harness shims in this repository.
---
# Topic
## Purpose
Explain when this repo-local skill is needed and when existing repo docs are enough.
## Agent Execution Standard
1. Discover current implementation.
2. Apply repo-specific workflow.
3. Confirm any shims stay aligned.
---
name: topic
summary: Create or update the repo-local topic workflow.
---
Follow `.agents/skills/topic/SKILL.md`.
interface:
display_name: 'Topic'
short_description: 'Create and validate the repo-local topic workflow.'
default_prompt: 'Use $topic to create or update the canonical repo-local topic workflow.'
Add and fix Detox E2E tests (smoke and regression) for MetaMask Mobile using withFixtures, Page Objects, and tests/framework. Use when creating a new spec, fixing a failing E2E test, adding page objects and selectors, or adding MetaMetrics analytics expectations (analyticsExpectations).
Write, fix, and update component view tests (*.view.test.tsx) for MetaMask Mobile using the tests/component-view/ framework. Use when creating a new view test file, fixing a failing view test, updating tests after a component change, or creating a new renderer or preset for a view.
Create and review E2E performance tests that measure real user flows on real devices with TimerHelper and PerformanceTracker. Use when creating, editing, or reviewing performance tests, when the user mentions perf tests, timing measurements, performance thresholds, or files in tests/performance/.
Creates or removes a git worktree using the project scripts and shared config. Use when the user asks to create a worktree, add a worktree, remove a worktree, delete a worktree, or work on a parallel branch in a separate directory.
Generate a CHANGELOG entry line for a pull request from code changes. Use when the user asks to write a changelog entry, fill the changelog section of a PR, or determine if changes are user-facing.
Identify code owners for changed files and map them to Slack group handles. Use when the user asks who owns changed files, which teams to tag for review, or to find code owners for a PR.