sina-noetfield-cloud

Manages GitHub and Vercel deployment workflows for the Noetfield public repository.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill sina-noetfield-cloud-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sina-noetfield-cloud
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/agent-skills/noetfield_cloud
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill sina-noetfield-cloud-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a public GitHub/Vercel repository healthy requires constant attention to CI status, README accuracy, deploy protection, and release tagging, which is easy to neglect alongside other work. ## Core Features & Use Cases - Repository Maintenance: Manages README, .github/ configuration, vercel.json, and deploy protection settings for the Noetfield ship repo. - Release Management: Keeps release tags current and CI pipelines green. - Lane Separation: Enforces strict workspace boundaries, never touching the local-only Noetfield-All-Documents SSOT or SourceA folders. - Use Case: A founder shipping updates through GitHub Actions (not Terminal) uses this agent to verify CI is green, cut a release tag, and confirm Vercel deploy protection is configured correctly. ## Quick Start Ask the agent to check CI status and prepare a release tag for the Noetfield GitHub repository.

Frequently Asked Questions about sina-noetfield-cloud

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

FAQPage Schema
How do I manage release tags and CI for a GitHub repository?

Use this agent to monitor CI status, keep release tags current, and verify workflows stay green in the Noetfield GitHub repo. It operates through GitHub Actions rather than direct Terminal commands.

How do I configure Vercel deploy protection for my project?

The agent manages `vercel.json` and deploy protection settings within the Noetfield ship repo. It focuses on keeping deployment configuration correct alongside README and `.github/` maintenance.

Can this agent edit my local documents or other repositories?

No. The agent is strictly scoped to the Noetfield cloud repo at `~/Desktop/Noetfield`. It is forbidden from touching `Noetfield-All-Documents` (the local SSOT) and `~/Desktop/SourceA`.

What are the limitations of this deployment workflow?

The workflow assumes the founder ships through GitHub Actions, not Terminal, and only covers the public cloud lane. Local-only hierarchy docs and research or site builds must be handled in their correct repos per the Agents Window guide.