saf-authoring

Update the Source Authority File with task learnings and validate front-matter.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/ssmleo/govfolio --skill saf-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: saf-authoring
Source: https://github.com/ssmleo/govfolio/tree/main/agents/skills/saf-authoring
Command: npx skills add https://github.com/ssmleo/govfolio --skill saf-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The Skill helps streamline the management and updating of the Source Authority File (SAF), ensuring it remains a reliable, up-to-date reference for all source-scoped activities.

Core Features & Use Cases

  • SAF Management: Automates the process of loading the SAF first, appending learnings, validating front-matter, and writing back to ensure consistency.
  • Workflow Optimization: Provides a structured checklist for core activities like task execution and validating front-matter, minimizing manual oversight.
  • Anti-Pattern Mitigation: Offers guidelines to avoid common pitfalls, such as leaving knowledge in transcripts or editing history instead of appending.

Quick Start

To maintain the SAF for a new PR, execute the 'saf-authoring' skill.

Frequently Asked Questions about saf-authoring

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

FAQPage Schema
How do I maintain a source authority file during a PR update?

To maintain a source authority file during a PR update, load the SAF, append task learnings, manually validate the front-matter, and write back to the repository to ensure source-scoped consistency.

What is the best way to update source authority files with new task learnings?

Updating source authority files requires appending new learnings rather than editing history, ensuring the canonical SAF remains a reliable, up-to-date reference without losing previous context.

How does source authority file management integrate with code repository workflows?

Source authority file management integrates with code repository workflows by operating within the repository and coordinating with source control operations like PR updates to synchronize learnings.

Do I need to manually validate front-matter when appending to a source authority file?

Yes, you need to manually validate front-matter when appending to a source authority file, as the workflow requires manual validation to ensure the updated metadata remains structurally consistent.

Why should I avoid leaving task knowledge in transcripts instead of the source authority file?

Avoiding leaving task knowledge in transcripts is necessary because the source authority file is the canonical reference; appending directly to the SAF mitigates this anti-pattern and centralizes repository learnings.

What limitations exist when using scripts to manage source authority files?

A key limitation when using scripts to manage source authority files is the requirement for manual front-matter validation, meaning the workflow cannot fully automate the metadata verification process.