Skip to content

rse/ase / plugin/skills/ase-sync-import

ase-sync-import

Verified

Import information from foreign sources into a set of artifact kinds (the target), generating or updating them to reflect the imported information. Use when the user wants to "import", "ingest", or "bring in" external sources like files, URLs, or pasted text into artifacts like SPEC, CODE, DOCS, TASK, INFR, or OTHR.

FileKindSize
SKILL.mdskill md8.8 KB
help.mdmarkdown3.0 KB

##  NAME

`ase-sync-import` - Import Foreign Sources into Artifact Set

##  SYNOPSIS

`ase-sync-import`
    [`--help`|`-h`]
    [`--target`|`-t` *target*[,...]]
    *hint*

##  DESCRIPTION

The `ase-sync-import` skill imports information from *foreign sources*
into a set of artifact kinds (the *target*), generating or updating the
target artifacts so they faithfully *reflect* the imported information.
Unlike `ase-sync-reconcile`, which syncs *between* existing ASE artifact
kinds, `ase-sync-import` brings in information from *external* sources
that live outside the ASE artifact sets.

The *foreign sources* are named by the free-form *hint* argument and may
be local files or directories, remote URLs, pasted text passages, or
references to other documents.

The *target* is a comma-separated list over the six recognized
artifact kinds `SPEC` (Specification, covering both requirements and
architecture), `CODE` (Source Code), `DOCS` (Documentation), `TASK`
(Task Plans), `INFR` (Infrastructure), and `OTHR` (catch-all). It
defaults to `SPEC`.

While importing, the skill honors the artifact formats of `SPEC` (the
*SpecBook* models and formats plus the *SpecBook* schema configuration)
and `TASK`; the kinds `CODE`, `DOCS`, `INFR`, and `OTHR` have
no dedicated format contract and are treated as free-form. A target
artifact that does not yet exist but is warranted by the imported
information is *generated* from scratch, while an existing target
artifact is *surgically updated* to reflect the imported information.
Generated or updated `SPEC` artifacts are validated via *SpecBook*
linting and the reported diagnostics are fixed in at most three rounds;
any remaining diagnostics are surfaced.

##  OPTIONS

-   `--target`|`-t` *target*[,...]:
    The comma-separated list of artifact kinds to generate or update.
    Defaults to `SPEC`. The skill errors out on an empty target or
    an unknown/unsupported kind.

##  ARGUMENTS

-   *hint*:
    The mandatory free-form description of the foreign sources to import
    from (e.g. a file path, directory, URL, or pasted text). The skill
    errors out on an empty hint.

##  SCENARIOS

-   You want external sources brought into the project artifacts
-   You want a foreign document, URL, or pasted text reflected in the `SPEC`
-   You want requirements from outside imported into a task plan
-   You want legacy material ingested into the specification

##  EXAMPLES

Import a foreign requirements document into the specification:

```text
❯ /ase-sync-import -t SPEC docs/legacy/requirements.txt
```

Import an external design write-up into the specification (the default
target), which covers the architecture, too:

```text
❯ /ase-sync-import https://example.com/design-notes.html
```

Import a pasted feature description into a task plan:

```text
❯ /ase-sync-import -t TASK the new export feature must support CSV and JSON
```

##  SEE ALSO

[`ase-sync-reconcile`](../ase-sync-reconcile/help.md),
[`ase-sync-export`](../ase-sync-export/help.md),
[`ase-task-implement`](../ase-task-implement/help.md).
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall