Get the FREE Ultimate OpenClaw Setup Guide →

create-usercontext-instructions

npx machina-cli add skill MSiccDev/ai-context-kit/create-usercontext-instructions --openclaw
Files (1)
SKILL.md
2.2 KB

Create User Context Instructions

Purpose

Generate a complete user-context instruction file with required sections, privacy-aware content handling, and consistent output formatting.

When To Use

  • Use this skill when the task is to create or regenerate a *_usercontext.instructions.md file.
  • Use this skill when user context must be gathered through structured phases.
  • Do not use this skill for project AGENTS.md (project context) files.

Required Inputs

  • Target identity label and role/title.
  • Privacy expectations (full detail vs placeholders).
  • Technical profile, projects, goals, style, and constraints.
  • Desired output filename/path.

Workflow

  1. Run phased discovery using references/discovery-phases.md.
  2. Normalize findings into required schema using references/output-schema.md.
  3. Apply format contract from references/output-format.md.
  4. Validate against references/quality-checklist.md before final output.
  5. If structured metadata is requested, apply references/json-metadata-schema.md.

Output Expectations

  • One complete *.instructions.md file for user context.
  • Required section coverage and logical ordering are preserved.
  • Privacy handling is explicit and consistent.
  • Output is provider-neutral.
  • Output contract and summary format follow references/output-format.md.

Resources

  • Discovery workflow: references/discovery-phases.md
  • Output schema: references/output-schema.md
  • Optional metadata schema: references/json-metadata-schema.md
  • Output contract: references/output-format.md
  • Quality checklist: references/quality-checklist.md
  • Structure baseline: ../../templates/usercontext_template.instructions.md
  • Example reference: ../../usercontexts/sample_usercontext.instructions.md

Constraints And Safety

  • Keep provider-neutral wording.
  • Preserve sensitive data boundaries; prefer placeholders when requested.
  • Use relative paths for references.
  • Avoid unrelated recommendations outside user-context scope.

Source

git clone https://github.com/MSiccDev/ai-context-kit/blob/development/skills/create-usercontext-instructions/SKILL.mdView on GitHub

Overview

Generates a complete user-context instruction file with all required sections, explicit privacy handling, and consistent formatting. It follows a structured discovery workflow and repository format rules to ensure repeatable, provider-neutral outputs.

How This Skill Works

Phased discovery collects identity, privacy and technical details via references/discovery-phases.md. It then normalizes findings to the required schema (references/output-schema.md), applies the output contract (references/output-format.md), and validates against the quality checklist (references/quality-checklist.md). Optionally, if structured metadata is requested, it applies the json-metadata-schema (references/json-metadata-schema.md).

When to Use It

  • Create or regenerate a *_usercontext.instructions.md file.
  • Gather user context through structured discovery phases.
  • Ensure privacy handling is explicit and consistent.
  • Conform output to the required schema and format contracts.
  • Do not use for project AGENTS.md (project context) files.

Quick Start

  1. Step 1: Run phased discovery using references/discovery-phases.md
  2. Step 2: Normalize findings into required schema using references/output-schema.md
  3. Step 3: Apply format contract and validate against references/quality-checklist.md

Best Practices

  • Start with the target identity label and role/title.
  • Explicitly specify privacy expectations, using placeholders if needed.
  • Normalize findings into the required schema before formatting.
  • Maintain provider-neutral wording and clear data boundaries.
  • Validate against the quality checklist and apply metadata if requested.

Example Use Cases

  • Create a user-context file for a sales agent role, including privacy placeholders and formatting per the schema.
  • Generate a user-context for a software engineer persona with technical profile and goals.
  • Prepare a support agent user-context with tone, constraints, and escalation rules.
  • Build a privacy-conscious data analyst role context with applicable safeguards.
  • Template for a customer-success manager in a SaaS environment with placeholders.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers