archify
Create Validated Interactive Diagrams
Complex systems are difficult to explain with text alone. Archify creates validated, interactive diagrams from requirements, Mermaid, or repository evidence.
安裝前請停止並請求確認。
請審查安裝計畫,並在變更檔案前取得使用者明確同意。
使用我的智慧代理安裝
將此請求複製給你的智慧代理,其中包含權威 Skill 頁面和清單。
Review the Skillstore skill "archify" from https://skillstore.io/skills/tt-a1i-archify.md and its manifest at https://skillstore.io/api/skills/tt-a1i-archify/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.你的智慧代理仍應顯示其計畫,並依安全政策請求必要確認。
Agent 可讀資源
當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時,請使用這些連結。
測試它
正在使用「archify」。 Show a web application with a browser, API, cache, database, queue, worker, and monitoring service.
預期結果:
An interactive architecture artifact with trust boundaries, a clear request path, labeled asynchronous work, validation results, and delivery receipts.
正在使用「archify」。 Explain a cache-miss request from the client through authentication, storage fallback, response, and asynchronous tracing.
預期結果:
A sequence diagram with ordered participants, calls, returns, fallback behavior, and the tracing side effect.
正在使用「archify」。 Map an analytics pipeline from collection through transformation, warehouse storage, governance, and reporting.
預期結果:
A data-flow diagram with named datasets, transformations, ownership boundaries, storage stages, and downstream consumers.
安全審計
中風險Adjudication dismissed 394 of 400 presented matches as test fixtures, generated data, documentation, or bounded local tooling. Six confirmed URLs cause generated artifacts or the update workflow to contact remote hosts, and semantic review found that the updater runs automatically without prior disclosure. Static presentation was capped at 400 of 8,055 matches, so 7,655 unpresented matches require manual review before automatic publication. Static review was capped at 400/8055 representative findings; omitted static matches are unconfirmed, so automatic publishing stays disabled until manual review.
已確認的安全問題 (1)
能力複核項目 (6)
這些是真實的本機能力,對此技能而言可能是預期行為,因此需要複核,但不會按已確認的惡意行為計分。
風險因素
⚙️ 外部命令 (50)
🌐 網路存取 (50)
📁 檔案系統存取 (50)
⚡ 包含腳本 (21)
🔑 環境變數 (50)
分享與引用此報告
分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據,不判斷該 Skill 是否安全。
複製報告連結
https://skillstore.io/skills/tt-a1i-archify/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown 徽章
[](https://skillstore.io/skills/tt-a1i-archify?utm_source=security_passport_badge)HTML 徽章
<a href="https://skillstore.io/skills/tt-a1i-archify?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/tt-a1i-archify/security.svg" alt="Skillstore security assessment" loading="lazy"></a>嵌入卡片
<iframe src="https://skillstore.io/embed/skills/tt-a1i-archify.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>學術引用 (APA · BibTeX · CFF)
APA 引用
tt-a1i. (2026). archify security audit report (audit version 4) [Author version 2.16]. Skillstore. https://skillstore.io/skills/tt-a1i-archify/audits/4BibTeX 引用
@techreport{tt-a1i-tt-a1i-archify-2026,
author = {tt-a1i},
title = {archify security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/tt-a1i-archify/audits/4},
note = {Author version 2.16}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "archify security audit report (audit version 4)"
version: "2.16"
type: report
authors:
- name: "tt-a1i"
date-released: "2026-08-31"
url: "https://skillstore.io/skills/tt-a1i-archify/audits/4"
identifiers:
- type: other
value: "skillstore:tt-a1i-archify:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore 評分
評分依據 證據置信度: 中你可以打造什麼
Document a Service Architecture
Map runtime components, trust boundaries, dependencies, and the primary request path for engineering documentation.
Explain an Operational Workflow
Show owners, decisions, approvals, failure paths, and rollback steps in a readable process diagram.
Trace Data and API Behavior
Visualize message order, asynchronous work, data transformations, storage, lineage, and downstream consumers.
試試這些提示
Create an architecture diagram for [system]. Show users, core services, storage, external dependencies, and the primary request path.
Convert this Mermaid [flowchart, sequenceDiagram, or stateDiagram] into a polished Archify diagram: [paste Mermaid]. Preserve meaning and labels.
Create a workflow for [process]. Separate owners into lanes and show approvals, blocking checks, failure handling, rollback, and recovery verification.
Inspect [repository path] and create an architecture diagram pinned to [commit]. Cite source evidence and mark every unsupported fact as unknown.
最佳實務
- Provide exact component names, boundaries, protocols, and known failure paths.
- Start with one primary path and add only details that improve understanding.
- Validate after each focused correction and deliver only after all required checks pass.
避免
- Do not invent repository facts, ownership, regions, protocols, or security boundaries.
- Do not add manual routing controls before diagnostics identify a geometry problem.
- Do not claim visual quality from automated checks without an actual visual review.
常見問題
Which diagram types are supported?
Can it convert Mermaid diagrams?
What output does it create?
Can it use repository evidence?
Does validation replace visual review?
Does it require network access?
開發者詳細資訊
作者
tt-a1i授權
MIT
作者版本
v2.16
Skillstore 修訂
r1
版本提示
作者聲明的版本不符合 SemVer 規範。
引用
0acc95b40c367e2016e824a72b27b83b507ef020
維護新鮮度
2026/9/8
使用量
0 次下載 · 0 次瀏覽
檔案結構
📁 assets/
📁 bin/
📁 delta/
📄 agent-tool-call.workflow.json
📄 async-job-roundtrip.sequence.json
📄 brand-aware-delivery.architecture.json
📄 cache-miss-request.sequence.json
📄 checkout-platform.base.architecture.json
📄 checkout-platform.head.architecture.json
📄 dataflow-product-analytics.html
📄 deployment-release.lifecycle.json
📄 incident-response.workflow.json
📄 product-analytics.dataflow.json
📄 production-deployment.architecture.json
📄 release-delivery.workflow.json
📄 sequence-cache-miss-request.html
📄 workflow-agent-tool-call-rendered.html
📄 LICENSE
📁 recipes/
📄 grid.mjs
📁 shared/
📄 cli.mjs
📄 i18n.mjs
📄 workflow-migration-geometry.mjs
📁 schemas/
📁 scripts/
📄 SKILL.md
📁 test/
📄 adaptive-reader-layout.test.mjs
📄 authored-reachability.test.mjs
📄 authoring-safety-contract.test.mjs
📄 automatic-port-spread.test.mjs
📄 base-input-compatibility.test.mjs
📄 chapter-delta-preview.test.mjs
📄 clean-skill-staging.test.mjs
📄 community-proof-intake.test.mjs
📄 desktop-reader-browser.test.mjs
📄 engineering-profile.test.mjs
📄 automatic-routing-node-border-clearance.workflow.json
📄 explicit-route.workflow.json
📄 explicit-viewbox.workflow.json
📄 agent-tool-call.workflow.json
📄 cache-miss-request.sequence.json
📄 product-analytics.dataflow.json
📄 production-deployment.architecture.json
📄 v1-workflow-700x400.workflow.json
📄 v1-workflow-explicit-coordinates.workflow.json
📄 generate-validators.test.mjs
📄 generated-artifact-xml.test.mjs
📁 helpers/
📄 xml.mjs
📄 ordinary-model-floor.test.mjs
📄 real-repository-proof.test.mjs
📄 relationship-direct-explorer.test.mjs
📄 relationship-permalink.test.mjs
📄 release-package-gates.test.mjs
📄 render-output-checks.test.mjs
📄 repository-evidence.test.mjs
📄 repository-language-metadata.test.mjs
📄 semantic-legend-gateway.test.mjs
📄 sequence-column-fit.test.mjs
📄 site-language-continuity.test.mjs
📄 site-language-integration.mjs
📄 stable-update-manifest.test.mjs
📄 story-beat-navigator.test.mjs
📄 story-director-strip.test.mjs
📄 story-follow-camera.test.mjs
📄 viewer-chrome-layout.test.mjs