How do I install the Ub Authoring skill?

Run npx skillmds@latest add gabrielmoreira/ub-authoring in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ub Authoring safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ub Authoring?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ub Authoring free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ub Authoring?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ub Authoring by gabrielmoreira — Agent Skill

Name: Ub Authoring
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Ub Authoring

Use this skill when the task involves creating, reviewing, or refactoring installable skills, shared skill references, or reusable agent-authoring guidance; when the work depends on routing-quality descriptions, non-use boundaries, naming, progressive disclosure, or cross-skill authoring conventions; or when you want to normalize skill and guidance structure without turning the task into a full customization-builder workflow. Do not use it for end-to-end customization generation, normal code implementation, or general repository planning.

gabrielmoreira Updated Sep 21, 2026 17 repo stars

File contents

UB Authoring

Mission

Use this skill to shape portable, installable authoring guidance for skills and related agent-behavior surfaces.

This skill owns the reusable authoring conventions that should travel with the skill catalog itself instead of living in repo-only docs or in one customization-specific skill.

When Not To Use

Do not use this skill for end-to-end customization generation; defer that to ub-customizations.
Do not use this skill for ordinary code implementation or framework work where no shared authoring contract is being changed.
Do not use this skill as a substitute for repo-local maintenance docs or packaging metadata that belong to a development repository rather than the distributable skill payload.

Embedded Contract

These rules are the base contract of this skill and must not depend on a secondary document to be applied correctly.

Treat descriptions as routing metadata, not marketing copy.
Add explicit non-use boundaries when wrong-skill activation is realistically costly or common.
Prefer concrete examples and acceptance boundaries over vague admonitions.
Keep the main skill surface lean and move deeper detail into targeted references.
Keep shared authoring guidance portable across installed skill payloads and avoid repo-local live truth in the reusable contract.
Keep reusable choice-question UX contracts in shared authoring guidance instead of re-encoding the same multiple-choice rules in each skill.

Load References On Demand

Read references/authoring-conventions.md when shaping shared skill structure, cross-skill wording, routing quality, reusable choice-question UX, or other reusable authoring patterns.

Core Workflow

Decide whether the task is changing a reusable authoring convention or a single skill's local content.
Keep portable shared guidance in this skill and domain-specific guidance in the owning skill.
Normalize descriptions, examples, non-use boundaries, and shared choice-question behavior only where the changed surfaces actually benefit from them.
Keep reusable references installable and avoid dead links into repo-only docs.

Output Requirements

When producing non-trivial authoring updates, include:

routing_note
boundary_note
reference_note
validation_note

Completion Checklist

Shared guidance remains portable inside .agents/skills/.
Description wording reads like routing logic, not inventory prose.
Non-use boundaries are explicit where misrouting is realistic.
Examples are concrete where abstract guidance would be easy to misapply.
Shared references avoid repo-only assumptions unless clearly labeled as such.

---name: ub-authoringdescription: Use this skill when the task involves creating, reviewing, or refactoring installable skills, shared skill references, or reusable agent-authoring guidance; when the work depends on routing-quality descriptions, non-use boundaries, naming, progressive disclosure, or cross-skill authoring conventions; or when you want to normalize skill and guidance structure without turning the task into a full customization-builder workflow. Do not use it for end-to-end customization generation, normal code implementation, or general repository planning.---# UB Authoring## MissionUse this skill to shape portable, installable authoring guidance for skills andrelated agent-behavior surfaces.This skill owns the reusable authoring conventions that should travel with theskill catalog itself instead of living in repo-only docs or in onecustomization-specific skill.## When Not To Use- Do not use this skill for end-to-end customization generation; defer that to `ub-customizations`.- Do not use this skill for ordinary code implementation or framework work where no shared authoring contract is being changed.- Do not use this skill as a substitute for repo-local maintenance docs or packaging metadata that belong to a development repository rather than the distributable skill payload.## Embedded ContractThese rules are the base contract of this skill and must not depend on asecondary document to be applied correctly.1. Treat descriptions as routing metadata, not marketing copy.2. Add explicit non-use boundaries when wrong-skill activation is realistically costly or common.3. Prefer concrete examples and acceptance boundaries over vague admonitions.4. Keep the main skill surface lean and move deeper detail into targeted references.5. Keep shared authoring guidance portable across installed skill payloads and avoid repo-local live truth in the reusable contract.6. Keep reusable choice-question UX contracts in shared authoring guidance instead of re-encoding the same multiple-choice rules in each skill.## Load References On Demand- Read `references/authoring-conventions.md` when shaping shared skill structure, cross-skill wording, routing quality, reusable choice-question UX, or other reusable authoring patterns.## Core Workflow1. Decide whether the task is changing a reusable authoring convention or a single skill's local content.2. Keep portable shared guidance in this skill and domain-specific guidance in the owning skill.3. Normalize descriptions, examples, non-use boundaries, and shared choice-question behavior only where the changed surfaces actually benefit from them.4. Keep reusable references installable and avoid dead links into repo-only docs.## Output RequirementsWhen producing non-trivial authoring updates, include:1. `routing_note`2. `boundary_note`3. `reference_note`4. `validation_note`## Completion Checklist- Shared guidance remains portable inside `.agents/skills/`.- Description wording reads like routing logic, not inventory prose.- Non-use boundaries are explicit where misrouting is realistic.- Examples are concrete where abstract guidance would be easy to misapply.- Shared references avoid repo-only assumptions unless clearly labeled as such.

Frequently asked questions