Skip to content
Back to search

shorts-guidelines

Agent skill for a daily autonomous two-agent routine on the publish-shorts project.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/orenatobr--shorts-guidelines/badge.svg)](/listings/orenatobr--shorts-guidelines)

HTML

<a href="/listings/orenatobr--shorts-guidelines"><img src="/api/listings/orenatobr--shorts-guidelines/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

For Claude Code, copy the skill folders into your personal skills directory:

git clone https://github.com/orenatobr/shorts-guidelines.git
mkdir -p ~/.claude/skills
cp -R shorts-guidelines/skills/* ~/.claude/skills/

Start a new Claude Code session. Skills load from the `description` in each `SKILL.md`, so they trigger on their own and can also be called by name.

Other agents: each skill is a folder with a `SKILL.md` (YAML frontmatter plus Markdown). Tools that read the Agent Skills format can load `skills/` as it is. For the rest, paste the body of the `SKILL.md` into the agent's instruction file.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 45 lines
  1. # shorts-guidelines
  2. A daily routine for the `publish-shorts` project. Two agents run in parallel: one audits yesterday's run and fixes code, the other analyzes engagement insights and proposes levers. The main session then reviews and merges the PRs, confirms the release and deploy, and writes notes. It is tied to that project, so read it as a worked example of a multi-agent daily routine.
  3. ## Install
  4. For Claude Code, copy the skill folders into your personal skills directory:
  5. ```bash
  6. git clone https://github.com/orenatobr/shorts-guidelines.git
  7. mkdir -p ~/.claude/skills
  8. cp -R shorts-guidelines/skills/* ~/.claude/skills/
  9. ```
  10. Start a new Claude Code session. Skills load from the `description` in each `SKILL.md`, so they trigger on their own and can also be called by name.
  11. Other agents: each skill is a folder with a `SKILL.md` (YAML frontmatter plus Markdown). Tools that read the Agent Skills format can load `skills/` as it is. For the rest, paste the body of the `SKILL.md` into the agent's instruction file.
  12. ## Usage
  13. Run `/shorts-guidelines` from the project directory. It also triggers on "daily run" and "shorts routine".
  14. ## Requirements
  15. The `publish-shorts` project, the `run-auditor` and `engagement-analyst` subagents, the `/daily-review` skill, `gh` and the GitHub MCP.
  16. ## Related skills
  17. It calls `git-guidelines`, `programming-best-practices` and `attack-protection`.
  18. ## What is in this repo
  19. | Path | Purpose |
  20. |------|---------|
  21. | `skills/shorts-guidelines/` | The `shorts-guidelines` skill. |
  22. | `CHANGELOG.md` | Notable changes, in Keep a Changelog format. |
  23. | `AGENTS.md` | Rules for AI agents that edit this repo. |
  24. ## Contributing
  25. `main` is protected: changes land through a pull request with one approval. See [AGENTS.md](AGENTS.md) for the conventions.
  26. ## License
  27. MIT, see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.