agentsclimarketplace

Create usercontext instructions

Skill MSiccDev/ai-context-kit/skills/create-usercontext-instructions

AI Context Kit provides a structured, instruction-based framework for context-aware AI collaboration across LLM providers. It includes authoritative specs, canonical templates, and skills workflows for creating and validating user context and project AGENTS.md files.

Install
npx -y skills add MSiccDev/ai-context-kit --skill create-usercontext-instructions

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Create complete user-context instruction files using a structured discovery workflow and repository format rules.

SKILL.md

2.7 KB, as published. Nobody here has run it

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.

How to Invoke

Load or attach this file's contents into your AI session to activate the workflow (paste, upload, or reference with #file:skills/create-usercontext-instructions/SKILL.md in VS Code Copilot Chat). In Claude Projects, add it to project knowledge. See Invoking Skills in the README for full platform guidance.

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. Stamp spec_version: "1.4.3" in the YAML frontmatter of the generated artifact.
  5. Validate against references/quality-checklist.md before final output.
  6. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.