Agent skill

Permit Data Fidelity Model

by h30190 in h30190/HJPLUS_Taiwan_Architect_KB

This skill should be used when designing storage, import/export, or database projections for legacy CPAMI permit-case data without losing its original string semantics.

CC-BY-SA-4.0Auto-check passedDatabases

Install Permit Data Fidelity Model

skills CLI
$ npx skills add h30190/HJPLUS_Taiwan_Architect_KB --skill permit-data-fidelity-model -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install h30190/HJPLUS_Taiwan_Architect_KB permit-data-fidelity-model --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/h30190/HJPLUS_Taiwan_Architect_KB.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'raw/設計軟體與工具/建管資料交換工具/保真資料儲存模型/permit-data-fidelity-model' .claude/skills/permit-data-fidelity-model && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
permit-data-fidelity-model
GitHub stars
158
Token cost
~1.4k tokens
SKILL.md length
582 words
Files
1
Skills in repo
86
Repo updated
First seen
Licence
CC-BY-SA-4.0

At a glance

This skill should be used when designing storage, import/export, or database projections for legacy CPAMI permit-case data without losing its original string semantics.

  • Works in 6 steps: Parse a legacy file through the format… → Validate that every core table and field… → Store the envelope in canonical JSONB… → …
  • Databases work in your project
  • SKILL.md covers Scope and trust boundary, Core invariants, Workflow and Synthetic worked example, plus 5 more sections
  • Needs INDEX_KEY

What it does

Permit Data Fidelity Model is an agent skill from h30190/HJPLUS_Taiwan_Architect_KB. This skill should be used when designing storage, import/export, or database projections for legacy CPAMI permit-case data without losing its original string semantics.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: claude-code,opencode,agent-skills

It sits in Databases. It works with PostgreSQL. The repository describes itself as: 一個開源的台灣AEC產業知識庫,只要你願意共享經驗與知識就歡迎加入我們. The licence is CC-BY-SA-4.0.

When your agent uses it

  • Databases work in your project

Example prompts

  • “/permit-data-fidelity-model”

Requirements

  • A credential in INDEX_KEY
  • Compatibility (from SKILL.md): claude-code,opencode,agent-skills

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Parse a legacy file through the format engine and create a versioned case envelope.
  2. Validate that every core table and field is present with string values; preserve empty strings rather than substituting null, zero…
  3. Store the envelope in canonical JSONB with schemaVersion, formSet, tables, and extraTables.
  4. Build text-first relational views for reporting; offer numeric/date conversions only as separate projected columns.
  5. Before normalized export, detect passthrough, unknown, and signed package tables/entries. Route them to the byte-preserving legacy-package…
  6. Round-trip using synthetic fixtures and compare the exported bytes where the input is expected to be unchanged.

What it can do on your machine

Read from SKILL.md and the folder at commit 35ed06e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • INDEX_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    claude-code,opencode,agent-skills

    From compatibility in the SKILL.md frontmatter.

Context cost

Permit Data Fidelity Model loads about 1.4k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 582 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from h30190/HJPLUS_Taiwan_Architect_KB at commit 35ed06e, republished under its CC-BY-SA-4.0 licence (© h30190). 582 words, ~1,378 tokens.

Download SKILL.mdSave it as .claude/skills/permit-data-fidelity-model/SKILL.md (or your agent's skills folder).
name
permit-data-fidelity-model
description
This skill should be used when designing storage, import/export, or database projections for legacy CPAMI permit-case data without losing its original string semantics.
compatibility
claude-code,opencode,agent-skills
type
Skill
license
CC-BY-SA-4.0
metadata.audience
architects
metadata.region
taiwan
metadata.class
C
metadata.status
unverified
metadata.data-currency
2026-07-16

Permit Data Fidelity Model

Scope and trust boundary

[Secondary] This is a persistence-design guide distilled from a pinned implementation plan. It is neither a legal definition of a permit record nor a certified production database design.[^postgres-plan]

Core invariants

  • [Secondary] Preserve every business value as a string, including leading zeros, "", dates, and Y/N/blank states.[^postgres-plan]
  • [Secondary] Treat the versioned JSONB payload as canonical. Relational tables or views are projections for query use, not the reconstruction source.[^postgres-plan]
  • [Secondary] Keep 13 core tables under tables and retain non-legacy groups under extraTables; do not flatten extensions into the legacy export.[^postgres-plan]
  • [Secondary] Use CP950 only at the import/export boundary. Database and exchange JSON operate in UTF-8.[^postgres-plan]
  • [Secondary] Keep a schema version and reject or migrate incompatible documents deliberately. Do not assume INDEX_KEY is globally unique.[^postgres-plan]
  • [Secondary] The normalized 13-table JSON-envelope export path applies only after detecting that the source has no passthrough, unknown, or signed package tables/entries. Route any such case to the byte-preserving legacy permit data interchange workflow, or reject it until lossless routing exists; never silently drop it.

Workflow

  1. Parse a legacy file through the format engine and create a versioned case envelope.
  2. Validate that every core table and field is present with string values; preserve empty strings rather than substituting null, zero, boolean, or numeric types.
  3. Store the envelope in canonical JSONB with schemaVersion, formSet, tables, and extraTables.
  4. Build text-first relational views for reporting; offer numeric/date conversions only as separate projected columns.
  5. Before normalized export, detect passthrough, unknown, and signed package tables/entries. Route them to the byte-preserving legacy-package workflow or reject the operation; only then validate CP950 encodability and serialize the fixed core tables in their required order.
  6. Round-trip using synthetic fixtures and compare the exported bytes where the input is expected to be unchanged.

Synthetic worked example

Store a fictional case with INDEX_KEY: "00123", an empty numeric-looking field "", and a land-number component "0007" as strings in payload.tables. A query view may expose NULLIF(value, '') as a numeric helper, but it must not overwrite the payload. An added equipment row belongs under payload.extraTables, not a fabricated core-table column.[^postgres-plan]

Show full SKILL.md (232 more words)Show less

Pitfalls

  • [Unverified] A 3NF-only canonical schema can erase field order, blank-versus-zero semantics, and compatibility fields; do not use it as the sole reconstruction source.
  • [Secondary] Do not make INDEX_KEY a unique primary key; use a surrogate document identity and treat it as a business index.[^postgres-plan]
  • [Secondary] Do not persist extensions by appending unknown groups to the legacy file; legacy export serializes core tables only.[^postgres-plan]
  • [Secondary] CP950 failures belong at export validation. Silent replacement characters are data loss.[^postgres-plan]

Privacy boundary

Payloads may contain identifiers, contact details, and other personal data. Keep fixtures fully synthetic, apply access control and encrypted backups in the receiving system, and do not copy payloads into documentation, issue discussions, or logs.[^postgres-plan]

Data Currency

The cited design snapshot is dated 2026-07-16. Revalidate before deployment.

To Verify

  • Confirm the active schema version and complete allowed extraTables list. Already checked: only the pinned planning snapshot. Next: inspect the active deployment schema.
  • Define migration, authorization, retention, backup, and incident-response controls. Already checked: the cited plan identifies these as target-system responsibilities. Next: obtain the receiving system's security design.
  • Run import/export and byte-level round-trip checks using synthetic fixtures on the deployed runtime. Already checked: the pinned plan names round-trip fidelity as its acceptance boundary. Next: execute the target runtime test suite.

[^postgres-plan]: Pinned implementation evidence, not legal authority: PostgreSQL integration plan.

© h30190, CC-BY-SA-4.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in raw/設計軟體與工具/建管資料交換工具/保真資料儲存模型/permit-data-fidelity-model of h30190/HJPLUS_Taiwan_Architect_KB.

Open the folder on GitHubat commit 35ed06e

Compare with similar skills

Permit Data Fidelity Model next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Permit Data Fidelity Model compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Permit Data Fidelity Model this skillh30190/HJPLUS_Taiwan_Architect_KB158—~1.4kAutomated safety check: PassCC-BY-SA-4.0
Backend Test WorkerCorrectRoadH/OpenTickly307—~1.3kAutomated safety check: PassAGPL-3.0
Ef Core Migrationsjihadkhawaja/Egroo178—~673Automated safety check: PassApache-2.0
Add Oliphaunt Extensionf0rr0/oliphaunt105—~1.4kAutomated safety check: PassMIT
Diagnose Cloud SessionFreakStudioCN/mpy-hardware-extension146—~809Automated safety check: NotesCustom licence
DB AdminEliasOulkadi/shokunin114—~2kAutomated safety check: NotesMIT

Similar skills

  • Backend Test Worker

    CorrectRoadH/OpenTickly

    Build and verify real-Postgres Go tests and thin transport smoke for tracking behavior.

    307 GitHub stars~1.3k tokensUpdated 7 days ago
    DatabasesAuto-check passed
  • Ef Core Migrations

    jihadkhawaja/Egroo

    Handle EF Core schema changes in Egroo. An agent skill from jihadkhawaja/Egroo.

    178 GitHub stars~673 tokensUpdated 6 mo ago
    DatabasesAuto-check passed
  • Add, update, or remove an Oliphaunt PostgreSQL contrib or external extension, including source pins, build recipes, target support, SDK metadata, release products, carrier identities, and package…

    105 GitHub stars~1.4k tokensUpdated today
    DatabasesAuto-check passed
  • Diagnose Cloud Session

    FreakStudioCN/mpy-hardware-extension

    用户报告 Blockless 扩展在云端实测时出问题(卡死/灰屏/跳步/构建失败),但本地复现不了、日志不在本地文件里时,用这个从云端托管数据库拉真实 session 定位症状与根因 / Use when a user reports an in-product Blockless bug from live cloud-backend testing and the real session…

    146 GitHub stars~809 tokensUpdated 11 days ago
    DatabasesAuto-check: notes
  • DB Admin

    EliasOulkadi/shokunin

    PostgreSQL database administration — backup/restore (pgdump, PITR, WAL archiving), health monitoring (connections, bloat, cache hit ratio, dead tuples), connection pooling (PgBouncer), replication…

    114 GitHub stars~2k tokensUpdated 4 days ago
    DatabasesAuto-check: notes
  • Postgresql Table Design

    ynulihao/AgentSkillOS

    Design a PostgreSQL-specific schema. An agent skill from ynulihao/AgentSkillOS.

    617 GitHub starsUsed in 15 repos~4k tokens
    DatabasesAuto-check passed

More from h30190/HJPLUS_Taiwan_Architect_KB

All 86 skills in this repo
  • Green Material Search Toolkit

    h30190/HJPLUS_Taiwan_Architect_KB

    This skill should be used when an architect or consultant needs to search Taiwan's TABC (財團法人臺灣建築中心) green building material certification database, assemble a set of qualified materials for a…

    158 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed
  • Skill Name Hyphenated

    h30190/HJPLUS_Taiwan_Architect_KB

    This skill should be used when [specific trigger scenarios].

    158 GitHub stars~791 tokensUpdated yesterday
    Auto-check passed
  • Taichung Land Parcel Query

    h30190/HJPLUS_Taiwan_Architect_KB

    This skill should be used when an architect receives just an address or lot number (地號) for a site in Taichung City, Taiwan, and needs the land's basic data — zoning, registered land area, land…

    158 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Permit Report Data Mapping

    h30190/HJPLUS_Taiwan_Architect_KB

    This skill should be used when mapping a legacy CPAMI permit report identifier to its actual BMS data groups, computed display fields, or unresolved template dependencies.

    158 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • Revit AI Targeting And Safe Execution

    h30190/HJPLUS_Taiwan_Architect_KB

    This skill should be used when an AI agent, MCP tool, Revit add-in, or automation must inspect or change a live Revit model and needs to prove its target set, choose bounded read-only context…

    158 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Smoke Exhaust Review

    h30190/HJPLUS_Taiwan_Architect_KB

    This skill should be used when evaluating smoke exhaust compliance for buildings in Taiwan, including windowless floor determination, smoke compartment partitioning, smoke exhaust window effective…

    158 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Permit Data Fidelity Model

What does Permit Data Fidelity Model do?

This skill should be used when designing storage, import/export, or database projections for legacy CPAMI permit-case data without losing its original string semantics. Permit Data Fidelity Model is an agent skill from h30190/HJPLUS_Taiwan_Architect_KB. This skill should be used when designing storage, import/export, or database projections for legacy CPAMI permit-case data without losing its original string semantics.

When should I use Permit Data Fidelity Model?

Permit Data Fidelity Model fits situations like: databases work in your project.

How do I install Permit Data Fidelity Model in Claude Code?

Run `npx skills add h30190/HJPLUS_Taiwan_Architect_KB --skill permit-data-fidelity-model -a claude-code`. Or copy the skill folder (raw/設計軟體與工具/建管資料交換工具/保真資料儲存模型/permit-data-fidelity-model in h30190/HJPLUS_Taiwan_Architect_KB) into .claude/skills/permit-data-fidelity-model in your project. Claude Code loads it when a task matches its description.

How do I install Permit Data Fidelity Model in Codex?

Run `npx skills add h30190/HJPLUS_Taiwan_Architect_KB --skill permit-data-fidelity-model -a codex`. Or copy the skill folder (raw/設計軟體與工具/建管資料交換工具/保真資料儲存模型/permit-data-fidelity-model in h30190/HJPLUS_Taiwan_Architect_KB) into .agents/skills/permit-data-fidelity-model in your project. Codex loads it when a task matches its description.

Can I use Permit Data Fidelity Model in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add h30190/HJPLUS_Taiwan_Architect_KB --skill permit-data-fidelity-model -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/permit-data-fidelity-model, .gemini/skills/permit-data-fidelity-model, .github/skills/permit-data-fidelity-model and .opencode/skills/permit-data-fidelity-model in your project.

What does Permit Data Fidelity Model need to run?

Going by SKILL.md and its folder, Permit Data Fidelity Model needs credentials named INDEX_KEY. Our summary lists: A credential in INDEX_KEY. Compatibility (from SKILL.md): claude-code,opencode,agent-skills.

Does Permit Data Fidelity Model access the network?

SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.

Is Permit Data Fidelity Model safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Permit Data Fidelity Model use?

Permit Data Fidelity Model is published under the CC-BY-SA-4.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Permit Data Fidelity Model use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Permit Data Fidelity Model?

Skills that share tags, products or a category with Permit Data Fidelity Model: Backend Test Worker (CorrectRoadH/OpenTickly, 307 stars), Ef Core Migrations (jihadkhawaja/Egroo, 178 stars), Add Oliphaunt Extension (f0rr0/oliphaunt, 105 stars) and Diagnose Cloud Session (FreakStudioCN/mpy-hardware-extension, 146 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Permit Data Fidelity Model?

h30190 (a GitHub user) maintains it in h30190/HJPLUS_Taiwan_Architect_KB, which has 158 GitHub stars. The repository holds 86 skills in this directory. The repository was last updated on October 8, 2026.

Source: h30190/HJPLUS_Taiwan_Architect_KB on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.