Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Productivity
Diy Pc Ingest
Ingest pasted PC parts purchase/config text (Discord message receipts, bullet lists) into Notion DIY_PC tables (PCConfig, ストレージ, エンクロージャー, PCInput). Use when...
skill openclawclawhub Free
Ingest pasted PC parts purchase/config text (Discord message receipts, bullet lists) into Notion DIY_PC tables (PCConfig, ストレージ, エンクロージャー, PCInput). Use when...
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, references/config.example.json, references/notion-ids.md, scripts/_deprecated/notion_apply_records.py, scripts/bootstrap_config.js
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.3
Provenance
- Publisher
- NEXTAltair
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Setup (required)
This skill is intended to be shared. Do not hardcode your Notion IDs or token in the skill. Copy the example config: skills/diy-pc-ingest/references/config.example.json → ~/.config/diy-pc-ingest/config.json Auto-bootstrap is disabled by default. Enable only when explicitly needed with DIY_PC_INGEST_BOOTSTRAP=1. Fill in your Notion targets (IDs): notion.targets.*.data_source_id (for schema/query) notion.targets.*.database_id (for creating pages) Provide Notion auth for notion-api-automation (notionctl): env: NOTION_API_KEY (recommended) or ~/.config/notion/api_key Notes: This skill uses Notion-Version 2025-09-03 by default. Targets are read at runtime from config; see references/config.example.json.
Data flow disclosure
Local input: pasted receipts/spec notes are parsed locally. External enrichment (optional): web_search/web_fetch may send partial product text to external web providers. Notion write path: records are queried/upserted via notion-api-automation/scripts/notionctl.mjs. Local config: ~/.config/diy-pc-ingest/config.json is read; write occurs only when bootstrap is explicitly enabled. Security rules: If user does not want external enrichment, skip web_search/web_fetch and proceed with local extraction only. Use minimal-scope Notion integration permissions (only target DIY_PC data sources).
Canonical Notion targets
Use data_sources endpoints for schema/query, and pages endpoint for row creation. (IDs are intentionally not included in this public skill. They live in your local config.)
Workflow (A: user pastes raw text)
Read the pasted text and decide target table per item: エンクロージャー: USB/RAID/HDDケース/ドック、ベイ数、JAN/型番、"安全な取り外し"表示名。 ストレージ: HDD/SSD/NVMe/SATA/容量/シリアル/健康状態。 PCConfig: CPU/GPU/RAM/PSU/MB/ケース/冷却/NIC/キャプチャ等。 Extract fields (best-effort). Prefer Japanese column names as they exist in each table. Enrich specs using web_search/web_fetch when it reduces user work (e.g., bay count, interface, capacity, form factor). Keep it minimal; don't overfill. Ask follow-up questions only for fields needed to avoid ambiguity or bad joins. ストレージ: Serial missing → ask for serial (or confirm creating as "暫定/シリアル不明"). エンクロージャー: ベイ数 or USB/Thunderbolt/LAN unclear → ask. PCConfig: Identifier/型番 missing but needed to match existing row → ask. If a key collides with multiple rows, do not write; ask user. Search existing records in Notion using scripts/notion_apply_records.js (auto-discovery mode): Provide JSONL records (one per item) on stdin. Script will: find an existing row by key (see below) report what would be created/updated/skipped without making changes Do not write anything (no create/update operations) Use this to preview results before actual upsert. Review search results and confirm with user: Show what would be created/updated/skipped Ask for confirmation before proceeding to actual upsert Upsert into Notion using scripts/notion_apply_records.js: Provide JSONL records (one per item) on stdin. Script will: find an existing row by key (see below) patch only missing fields unless overwrite=true otherwise create a new row Report results (created/updated/skipped) and link any created rows. 3
Upsert keys (rules)
ストレージ: シリアル (exact) is the primary key. If the existing row was created without serial, allow a safe fallback match by title + (optional) 購入日/価格(円) to support post-fill of serial/health/scan-date. エンクロージャー: 取り外し表示名 (exact) else title/name. PCConfig: (Name + Purchase Date) を複合キーとして扱う（exact）。重複ヒット時は書き込まず質問。 If a key collides with multiple rows, do not write; ask user.
JSONL input format for the apply script
Each line is a JSON object: {"target":"enclosure","title":"RATOC RS-EC32-R5G","properties":{"種別":"USBケース","接続":"USB","ベイ数":2,"普段つないでるPC":"RECRYZEN","購入日":"2026-01-18","購入店":"PCワンズ","価格(円)":8977,"取り外し表示名":"RS-EC32-R5G","メモ":"JAN: 4949090752191"}} Optional control fields (for cleanup / manual fixes): page_id (or id): update this Notion page directly (bypasses upsert matching) archive: true: archive the page (useful for de-dup) overwrite: true: allow overwriting existing values (including clearing with null) Optional behavior flags: mirror_to_pcconfig: true (only for target=storage): also create/update a pcconfig row for the installed component. requires: 現在の接続先PC, 購入日, Name Targets: enclosure | storage | pcconfig | pcinput Property value encoding: select/status: string name rich_text: string number: number date: YYYY-MM-DD checkbox: boolean relation: array of page_ids (advanced; avoid unless needed)
Notes
Always use Notion-Version 2025-09-03. Prefer POST /v1/data_sources/{id}/query over /databases/{id}/query. Relation schema updates require relation.data_source_id (not database_id).
Note (implementation)
JS implementation is the default: scripts/notion_apply_records.js Legacy Python implementation is kept for reference: scripts/_deprecated/notion_apply_records.py
Notion tooling (recommended)
Install notion-api-automation via ClawHub for Notion API debugging: clawhub install notion-api-automation This skill does not depend on skills/notionkit/*. Primary ingestion path is scripts/notion_apply_records.js; use skills/notion-api-automation/scripts/notionctl.mjs for diagnostics/manual API operations.
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs2 Scripts1 Config
- SKILL.md
- README.md
- references/notion-ids.md
- scripts/_deprecated/notion_apply_records.py
- scripts/bootstrap_config.js
- references/config.example.json