Asp Artifact En

Decision Flow

1. If the user wants to find or review an artifact, call list_artifacts.
2. If the user wants to attach intelligence, analysis notes, or structured analysis to an artifact, use the asp-enrichment-en skill.
3. If the user is investigating from an artifact, treat the artifact as the smallest pivot object and suggest the next most useful hop only when needed.

SOP

List Artifacts

1. Extract the narrowest useful filters from the request.
2. Call list_artifacts.
3. Parse the returned JSON strings.
4. Present a compact artifact view. If the user will likely attach or reuse the artifact next, surface the artifact rowid explicitly.

Preferred response structure:

Then add one short explanation line when needed.

Clarification Rules

• Ask for artifact_id only when the user wants to enrich an existing artifact and did not provide it.

Output Rules

• Be concise.
• Do not output raw JSON unless the user explicitly asks for it.
• Prefer pivot-oriented wording over storage wording.
• When many artifacts match, show the most valuable subset and briefly explain the overall pattern.

Failure Handling

• If no artifacts match, say so directly and suggest the most useful refinement.
• If the target artifact does not exist, say so directly.