multica-artifact-architect SKILL.md skillA
multica-artifact-architect from it235/multica-best-practices is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add it235/multica-best-practices/multica-artifact-architect@git:20260910.699a593Pins git:20260910.699a593 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- it235/multica-best-practices
- Path
templates/en_US/skills/architect/multica-artifact-architect/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260910.699a593, committed Sep 10, 2026
- Size
- 2,038 bytes
- Repository stars
- 237
- License
- MIT
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Artifact · Technical Design Sync ## Purpose Land technical design docs to the team's unified technical-doc location and let downstream retrieve them via a stable reference. > This skill decouples "platform integration" from "role prompt": the role prompt only says "produce technical design", not which platform. Changing companies means editing only this skill, not the @Architect prompt. ## Default platform: Git repo / Confluence (choose one per team convention) - Output: technical design (current arch, proposed change, affected components, steps, verification plan, risks). - Upload A (Git repo): place under the repo's agreed doc dir (e.g. `docs/design/<issue-id>.md`), reviewed together with the code PR — traceable. - Upload B (Confluence): create / update a technical design page, return the link. - Retrieve: downstream @FrontendDev / @BackendDev / @Tester read via the **file path or page link**. ## Content spec (platform-independent part) Per `multica-technical-design` skill: current architecture, minimal viable change, affected components, implementation steps, verification plan, risks. Keep stable headings and ids. ## Usage (role side writes only this line) …
Read the whole file at its exact version.
How to install
mdr add it235/multica-best-practices/multica-artifact-architect@sha256:f0990aab4513be7dThe line at the top of this page pins the label git:20260910.699a593, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_un6ll3o6nwqybjm6)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 10, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2038 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
it235/multica-best-practices · 237 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_un6ll3o6nwqybjm6 GET https://markdownregistry.com/api/v1/resolve?ref=it235/multica-best-practices/multica-artifact-architect GET https://markdownregistry.com/api/v1/blob/f0990aab4513be7dca69158330648586fbf553028984bc5e2660150475124764
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from it235/multica-best-practices
Every file in it235/multica-best-practices