Skip to content
Back to skills

Use Artifacts

ASecurity

Create Claude-style local HTML artifacts under ~/.agents/artifacts. Use when building plans, prototypes, visualizations, dashboards, diagrams, options, or reusable standalone pages.

  • 3 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 5, 2026
designpythongobashapisecurity

Works with

  • api

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 22, 2026

npx -y skills add twikus/claude-configuration --skill use-artifacts --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Use Artifacts?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Use Artifacts
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/twikus-use-artifacts/badge)](https://www.skillsdirectory.com/skills/twikus-use-artifacts)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: use-artifacts
description: Create Claude-style local HTML artifacts under ~/.agents/artifacts. Use when building plans, prototypes, visualizations, dashboards, diagrams, options, or reusable standalone pages.
disable-model-invocation: true
user-invocable: true
---

Create a standalone HTML artifact only when the work is substantial, visual or reusable, and does not belong in a product repo. Skip tiny answers and in-repo product changes unless asked.

Always write to `~/.agents/artifacts/<id>/`. Never write a repo-local `.agents/artifacts`.

Pick a kind: `variations` `croquis` `thinking` `feature-plan` `security-review` `implementation-plan` `interactive` `dashboard` `visualization` `document` `diagram` `prototype` `reference`. Default to a thinking page. Any plan kind must include both a content draft and croquis. Interactive only when the user asks for a mini-app or controls. Variations: 3–6 full-width rows of low-fidelity options, no masthead, no leading ranking.

Style in this order: the user's words, then the app's real tokens (match its theme exactly), then a subject-specific identity. Sketch color, type, and layout in `HIGHLOGIC.md` before HTML. Define tokens on `:root` and both color schemes unless the identity is deliberately single-theme, recorded in `HIGHLOGIC.md`. Restyle the scaffold; never ship its placeholder look. No secrets, no Anthropic API, no CDN fonts.

Scaffold with:

```bash
python3 ~/.agents/skills/use-artifacts/scripts/create_artifact.py "<short title>" --style "<requested, project:app-name, or subject-specific>" --kind thinking
```

If the page needs download or local data, inline `~/.agents/skills/use-artifacts/assets/local-runtime.js` in a `<script>` tag (no `src`) and record `capabilities` in `manifest.json`. Web research goes through `$exa-search`.

Keep `index.html`, `HIGHLOGIC.md`, and `manifest.json` current. On a substantial rewrite, copy `index.html` to `versions/<timestamp>-index.html` first.

Verify by opening `index.html` (serve the folder only if the browser requires it). Stop when you return the local `index.html` path, the selected style, and what you verified.

Files in this skill

  • SKILL.md18.4 KB
  • agents/openai.yaml348 B
  • assets/codex-icon.svg692 B
  • assets/local-runtime.js11.3 KB
  • scripts/create_artifact.py8.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…