domain-profiles_skill

This skill provides domain-specific configuration profiles for research and writing, guiding search strategies, terminology, and content structure across
  • Shell

6

GitHub Stars

6

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill bityoungjae/marketplace --skill domain-profiles

  • arts.md8.9 KB
  • history.md7.7 KB
  • language.md8.5 KB
  • science.md7.9 KB
  • SKILL.md3.8 KB
  • technology.md7.8 KB

Overview

This skill provides domain-specific configuration profiles for creating learning resources across technology, history, science, arts, and general domains. It standardizes search strategies, domain metadata fields, terminology policies, and recommended content structures so researcher and writer agents behave appropriately for each subject area.

How this skill works

Agents load a profile file for the chosen domain and extract only the sections they need (search strategy, special fields, terminology policy, content structure, or review criteria). The skill maps input domain names to specific Markdown files and prescribes which sections each agent type should use. When domain is unclear or set to general, the language profile is used as a fallback.

When to use it

  • During research collection (Phase 2 of initialization) to drive domain-appropriate searches
  • When a researcher agent needs authoritative search patterns and source guidance
  • When a writer agent needs domain-adapted document structure and terminology rules
  • When assembling a persona or guidelines with domain-specific sections
  • When a reviewer agent needs targeted review criteria for quality and style checks

Best practices

  • Always load the profile via the standardized Read("skills/domain-profiles/{domain}.md") pattern
  • Map the input domain name to the exact file name (use language.md for general)
  • Extract only the sections relevant to the agent role to avoid information overload
  • Prefer authoritative sources and domain-specific search patterns listed in the profile
  • Use the terminology policy to decide when to define terms, translate, or cite

Example use cases

  • A researcher agent reads technology.md to generate API and framework search queries
  • A writer uses history.md content structure to build timelines, primary-source excerpts, and contextual analysis
  • A science curriculum author follows science.md special fields to collect formulas, units, and experiment safety notes
  • An arts educator applies arts.md pedagogy suggestions to structure technique lessons and portfolio prompts
  • A general educator loads language.md for broad-topic resource templates and language-focused guidance

FAQ

Use language.md; there is no general.md file. The language profile contains broadly applicable patterns.

Which sections should each agent extract?

Researchers: Search Strategy, Special Fields, Quality Indicators. Research-collectors: Search Strategy, Special Fields. Writers: Content Structure, Terminology Policy. Reviewers: Review Criteria.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational