skills.rest
Noetfield-Systems
Noetfield-SystemsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sina-ai-dev-bridge-os

Generates G1/G2/G3 wire lane evidence artifacts for AI Dev Bridge OS repositories.

Updated Jun 20, 2026
Search Tags:#devops#github actions#tailscale#evidence artifacts#wire lane#runreceipt#relay proof
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill sina-ai-dev-bridge-os-noetfield-systems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sina-ai-dev-bridge-os
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/agent-skills/ai_dev_bridge_os
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill sina-ai-dev-bridge-os-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating proof-of-work evidence across wire lanes (G1/G2/G3) in the AI Dev Bridge OS repo requires consistent tracking of Tailscale connectivity, relay proofs, and RunReceipt stubs, which is error-prone when done manually. ## Core Features & Use Cases - Wire Lane Evidence Production: Generates G1/G2/G3 proof artifacts in scripts/evidence/ and maintains WIRE_LANE_PROGRESS.md. - RunReceipt Wire Stubs: Supports P0 RunReceipt wire stubs for the factory thread workflow. - Scope Guardrails: Operates only within the AI Dev Bridge OS repo and never edits SourceA hub code, keeping hub laws read-only. - Use Case: An executor runs shell commands to produce Tailscale relay proof artifacts while the founder wires GitHub Actions, with all progress recorded in the wire lane tracker. ## Quick Start Ask the agent to produce G1 wire lane evidence and update WIRE_LANE_PROGRESS.md in the AI Dev Bridge OS repo.

Frequently Asked Questions about sina-ai-dev-bridge-os

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate G1/G2/G3 wire lane evidence in AI Dev Bridge OS?▼

Wire lane evidence is produced by running shell commands as the executor and storing artifacts in the scripts/evidence/ directory. Progress is recorded in WIRE_LANE_PROGRESS.md, with the founder wiring GitHub Actions when lanes are ready.

What is WIRE_LANE_PROGRESS.md used for?▼

WIRE_LANE_PROGRESS.md tracks the status of G1, G2, and G3 wire lane proofs in the AI Dev Bridge OS repo. It serves as the central record for Tailscale and relay evidence produced during the bridge workflow.

Can this skill edit SourceA hub code?▼

No, the skill explicitly forbids editing the SourceA directory. Hub laws may only be read; all write operations are confined to the AI Dev Bridge OS repository workspace.

What are RunReceipt wire stubs in the factory thread?▼

RunReceipt wire stubs are P0-priority placeholder artifacts supporting the factory thread workflow. They define the wiring points where factory run receipts will later connect to the bridge evidence pipeline.

Who executes the shell commands for wire lane proofs?▼

The executor agent runs shell commands to generate proof artifacts, while the founder handles GitHub Actions wiring. This division keeps evidence production separate from CI configuration.

Related Skills

Explore More Software Engineering Skills→
magnus919magnus919
40

headscale-derp

Deploy and manage DERP relay servers for Tailscale and Headscale networks.

Community
Advanced
EvoClawEvoClaw
11

using-amplify

Enforce one-phase-per-turn research workflows with mandatory gates G1 through G4.

Official
Advanced
adaptive-enforcement-labadaptive-enforcement-lab
3

hardened-release-workflow

Automate hardened release workflows with signed artifacts and SLSA provenance.

Official
Advanced
volcenginevolcengine
28.1k

tmux

Send keystrokes and scrape pane output to control tmux sessions.

Official
Intermediate