Agents · documentation

Skill Architect

Turns a job you repeat into a SKILL.md with inputs, a method, checks, and a deliverable.

Purpose

Convert one recurring job into a portable skill file.

Deliverable: Marketplace listing and a SKILL.md you can install.

Inputs

Required

  • Skill name
  • The job
  • Required inputs
  • Steps you already use
  • The deliverable

Optional

  • What the skill must not do

Method

  1. 01Take the name, job, inputs, and steps from the brief only.
  2. 02If steps were written, keep them in that order and mark them as yours.
  3. 03If no steps were written, propose the standard six-step production loop and say it is a proposal.
  4. 04Leave every missing contract field as not supplied. Do not invent a domain method.
  5. 05Write SKILL.md with activation rules, evidence rules, and a QA checklist.

Evidence

A run uses the text you submit. It does not browse, and it does not open links you paste.

  • Do not: Invent a workflow you did not describe and call it current practice.
  • Do not: Bundle several jobs into one skill.

Quality checks

  • The job in the file is the job you typed.
  • No step is presented as your current process unless you wrote it.
  • No URL, statistic, or tool was added.

SKILL.md

Install at ~/.grok/skills/skill-architect/SKILL.md and start a new session.

Download
---
name: skill-architect
description: Turns a job you repeat into a SKILL.md with inputs, a method, checks, and a deliverable.
---

# Skill Architect

## Purpose
Convert one recurring job into a portable skill file.

Outcome: Marketplace listing and a SKILL.md you can install.

## When to activate
Use this when the user needs to convert one recurring job into a portable skill file.

## When not to activate
- Invent a workflow you did not describe and call it current practice.
- Bundle several jobs into one skill.

## Required inputs
- Skill name
- The job
- Required inputs
- Steps you already use
- The deliverable

## Optional inputs
- What the skill must not do

## Workflow
1. Take the name, job, inputs, and steps from the brief only.
2. If steps were written, keep them in that order and mark them as yours.
3. If no steps were written, propose the standard six-step production loop and say it is a proposal.
4. Leave every missing contract field as not supplied. Do not invent a domain method.
5. Write SKILL.md with activation rules, evidence rules, and a QA checklist.

## Evidence
- Verified facts are only pages retrieved in the run, or figures and sentences the user typed.
- Label user-provided claims, assumptions, and unknowns separately.
- Do not invent sources, statistics, quotations, contacts, credentials, or tool use.
- Do not say a page, file, or account was opened if it was not.
- Do not present the output as regulated professional advice.

## Output
Marketplace listing and a SKILL.md you can install.

## Quality checks
- [ ] The job in the file is the job you typed.
- [ ] No step is presented as your current process unless you wrote it.
- [ ] No URL, statistic, or tool was added.

## Failure handling
If a required input is missing, return the sections that can be completed and name the gap. Do not fill it.

## Safety
Refuse deception, impersonation, and requests for wrongdoing. Do not collect credentials.

## Install
Save as ~/.grok/skills/skill-architect/SKILL.md and start a new session.

Related

Research skills show only pages retrieved on that run. Every other skill uses what you type and labels the gaps. Finance outputs are planning support, not regulated advice. Nothing here is an identity, credit, legal, medical, or compliance decision.