artifact
Skill2 starsChanged 53 days agoMITView on GitHub
Delivers what the owner asked for as an artifact they can open in the live office: an interactive prospecting file, a CSV, a dashboard, a comparison table, a one-page page. Use whenever the owner asks for "a file", "a list", "a table", "a dashboard", "a page" or "something I can open".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- MasihMoafi/skillstheir own version, first seen Nov 3, 2026
- maotoumao/Cebiantheir own version, first seen Oct 24, 2026
- gvieira18/skillstheir own version, first seen Oct 20, 2026
- yacb2/aidextheir own version, first seen Oct 9, 2026
- cgoinglove/thursdaytheir own version, first seen Sep 27, 2026
- cgoinglove/thursday-agenttheir own version, first seen Sep 27, 2026
Used with
Projects with it also use shadcn and skill-creator.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
DatabricksSkillshadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- maotoumao/Cebian★ 181same name
- cgoinglove/thursday★ 56same name
- cgoinglove/thursday-agent★ 56same name
- MasihMoafi/skills★ 8same name
- yacb2/aidex★ 2same name
- gvieira18/skills★ 1same name
- watzon/claude-code★ 1same name
- xiagaohui/local-artifacts-for-claude-code★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- draft-outreachSkill
- follow-upsSkill
- knowledgeSkill
- meeting-briefSkill
- one-pagerSkill
- proposalSkill
- prospectSkill
- qualifySkill
- quote-invoiceSkill
- repliesSkill
- setupSkill
- sprintSkill
- artifactSkill
- draft-outreachSkill
- follow-upsSkill
- knowledgeSkill
- meeting-briefSkill
- one-pagerSkill
- proposalSkill
- prospectSkill
- qualifySkill
- quote-invoiceSkill
- repliesSkill
- setupSkill
- sprintSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
All data embedded in the page, taken from the workspace files, with sources shown.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Artifact
- Understand the request in one line: what, for whom, which data, which filters. If the data does not
exist yet (for example no leads), say so and propose the command that creates it (
prospect 10). - Prospecting file (the most common): run
node tools/artifact.mjs prospects --title "<title in the owner's language>" --lang <fr|en> [--tier hot,warm] [--status ...] --as sales. The page is built from the real files: search, filters, sort, sources, draft messages, personal notes and CSV export. Never retype leads into a page by hand. - Table for Excel:
node tools/artifact.mjs csv --title "..." [--tier ...] --as sales. - Any other page (dashboard, comparison, map, one-pager, calculator): write one self-contained
HTML file in
workspace/tmp/<name>.html, thennode tools/artifact.mjs new --title "..." --file workspace/tmp/<name>.html --as <role>.- All data embedded in the page, taken from the workspace files, with sources shown.
- Scripts only from cdn.jsdelivr.net, cdnjs.cloudflare.com or unpkg.com; no calls to other sites.
- Clean and readable: light background, one accent color, system font, works on a phone.
- Interactive when useful: filters, sort, tabs, a small chart. Numbers computed in the page from the embedded data, never typed from memory.
- Tell the owner in 2 lines what the artifact contains and that it is in the Artifacts tab.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.