Skip to content
Back to search

cstack

Reusable agent skills by Charles Zheng. Starting with Reflect: evidence-backed reviews of outcomes and efficiency.

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/goodnight000--cstack/badge.svg)](/listings/goodnight000--cstack)

HTML

<a href="/listings/goodnight000--cstack"><img src="/api/listings/goodnight000--cstack/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.

Clone the repository:

git clone https://github.com/goodnight000/cstack.git
cd cstack

Choose a skill, then link it into your agent's skills directory. Run the appropriate commands from the repository root.

skill_name=reflect  # or rsi, video-edit, animated-video, video-script, asset-library

To install the video skills together, run either block below once per name in `video-script video-edit animated-video asset-library`, or wrap it in `for skill_name in video-script video-edit animated-video asset-library; do … done`.

For Codex:

mkdir -p "$HOME/.codex/skills"
test ! -e "$HOME/.codex/skills/$skill_name" && \
  ln -s "$PWD/skills/$skill_name" "$HOME/.codex/skills/$skill_name"

For Claude Code:

mkdir -p "$HOME/.claude/skills"
test ! -e "$HOME/.claude/skills/$skill_name" && \
  ln -s "$PWD/skills/$skill_name" "$HOME/.claude/skills/$skill_name"

If the selected skill is already installed, compare and back up that version before replacing it. If both agents share a skills directory, install once. You can copy the folder instead of linking it; a linked installation follows changes in this checkout. Reload your agent session after installation if needed.

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 · 228 lines
  1. # cstack
  2. These are the skills that I use almost every day. I am always adding more skills here. The skills here have saved me hours on on workflows. lmk your experiences with them and drop any feedback! These skills are also refined quite often.
  3. ## Skills
  4. | Skill | What it does |
  5. | --- | --- |
  6. | [reflect](skills/reflect/SKILL.md) | Reviews outcomes and efficiency, shows findings before asking for feedback, and proposes improvements for approval. Works with completed, incomplete, and unsuccessful sessions. |
  7. | [rsi](skills/rsi/SKILL.md) | Tests changes to agent skills, instructions, tools, and working processes against the current version, with bounded runs and evidence for keeping or rejecting each change. |
  8. | [video-edit](skills/video-edit/SKILL.md) | Edits talking-head videos, reels, skits, recreations, demos, and screen recordings. Covers audio recovery, take selection, supporting visuals, captions, Resolve or FFmpeg edits, and final-export checks, with optional style packs per format. |
  9. | [animated-video](skills/animated-video/SKILL.md) | Makes animated videos in code with Remotion, in 2D or 3D: explainers, character stories, motion graphics, kinetic type, and animated infographics. Finds inventive pictures with a separate brainstorm and picker, picks a visual style from side-by-side style frames (optional style packs give head starts), gets a key-frame board approved, times everything from the voiceover, animates in parallel with sound cued to picture events, and reviews renders by frames and audio measurements. |
  10. | [video-script](skills/video-script/SKILL.md) | Brainstorms short-form video ideas and writes scripts from the creator's own analytics: who has a stake, a hook that lands in 3 seconds, a second sentence that keeps viewers, and proof on screen. Also turns posted-video insights into lessons, with a script that reads retention curves from screenshots. |
  11. | [asset-library](skills/asset-library/SKILL.md) | Keeps one local library of reusable footage, images, music, sound effects, characters, animation code and 3D sets across projects. Agents search it before sourcing or building, register something as a versioned bundle when another project is about to reuse it, and can record which version a delivered cut used. |
  12. Each skill lives in its own directory under `skills/` and can be installed separately.
  13. ## The video skills together
  14. video-script writes the script and stops. video-edit makes edits of camera footage;
  15. animated-video makes films drawn in code. The deliverable decides which of the two owns the
  16. final timeline: an edit with animated shots is video-edit's, and animated-video builds the
  17. shots to its brief; an animated film is animated-video's, even with one camera insert.
  18. asset-library is shared by both.
  19. Every one works alone. Without asset-library, video-edit and animated-video keep a manifest
  20. in the project instead of a shared library, and nothing else changes. Install all four to get
  21. reuse across projects.
  22. ## Install
  23. Clone the repository:
  24. ```sh
  25. git clone https://github.com/goodnight000/cstack.git
  26. cd cstack
  27. ```
  28. Choose a skill, then link it into your agent's skills directory. Run the appropriate commands from the repository root.
  29. ```sh
  30. skill_name=reflect # or rsi, video-edit, animated-video, video-script, asset-library
  31. ```
  32. To install the video skills together, run either block below once per name in
  33. `video-script video-edit animated-video asset-library`, or wrap it in
  34. `for skill_name in video-script video-edit animated-video asset-library; do … done`.
  35. For Codex:
  36. ```sh
  37. mkdir -p "$HOME/.codex/skills"
  38. test ! -e "$HOME/.codex/skills/$skill_name" && \
  39. ln -s "$PWD/skills/$skill_name" "$HOME/.codex/skills/$skill_name"
  40. ```
  41. For Claude Code:
  42. ```sh
  43. mkdir -p "$HOME/.claude/skills"
  44. test ! -e "$HOME/.claude/skills/$skill_name" && \
  45. ln -s "$PWD/skills/$skill_name" "$HOME/.claude/skills/$skill_name"
  46. ```
  47. If the selected skill is already installed, compare and back up that version before replacing it. If both agents share a skills directory, install once. You can copy the folder instead of linking it; a linked installation follows changes in this checkout. Reload your agent session after installation if needed.
  48. ## Use Reflect
  49. Ask your agent:
  50. ```text
  51. Use the reflect skill to review this session, including the result and any avoidable effort.
  52. Show me the findings and proposed changes before editing reusable instructions.
  53. ```
  54. You can also name other threads and a time window when your agent has access to their history. Reflect does not provide its own history connector.
  55. The review separates consequential findings from changes worth adding to reusable guidance. It can report an inefficiency without recommending another rule. It asks for approval before editing instructions and does not authorize publication, memory changes, or resuming the reviewed task.
  56. ## Use RSI
  57. ```text
  58. Use the rsi skill to test one improvement to this agent workflow.
  59. Reuse our Reflect findings, compare with the current version, and state a bounded
  60. experiment plan. Keep installed instructions unchanged until I approve adoption.
  61. ```
  62. RSI uses the project's existing runners and checks. It can reuse Reflect when installed,
  63. or reconstruct the necessary evidence directly. It adds no background service or test
  64. platform. Give it the task, experiment budget, and adoption scope; it preserves those
  65. bounds across the work. A successful local comparison is evidence for the tested scope,
  66. not proof of unlimited recursive improvement.
  67. ## Use Video Edit
  68. ```text
  69. Use the video-edit skill to edit the footage in this project.
  70. Start from the latest accepted version and the brief. Preserve complete takes,
  71. use supporting visuals that match the spoken claims, and check the actual export.
  72. ```
  73. On first use the skill runs `scripts/preflight.py`, which checks for FFmpeg,
  74. Python 3, and [uv](https://docs.astral.sh/uv/), which runs local transcription
  75. (Phonon on Apple silicon, Whisper elsewhere).
  76. It shows the install command for anything missing and runs it only if you agree.
  77. [DaVinci Resolve](https://www.blackmagicdesign.com/products/davinciresolve) (free)
  78. is recommended for a native, editable project; without it the skill renders with
  79. FFmpeg. Browser research and publishing need browser tools and your accounts.
  80. With no brief, the skill asks where the video will be posted, how long it should
  81. be, and whether you want music, sound effects, or a hook headline, then follows
  82. its [talking-head style pack](skills/video-edit/styles/talking-head/README.md). To keep
  83. your own defaults across updates, put them in `~/.video-edit/profile.md`.
  84. Of the bundled [sound effects](skills/video-edit/assets/sfx/README.md), 33 are
  85. CC0 Freesound recordings; the other 28 are not covered by the MIT license and
  86. their sources and unverified rights status are listed in their catalog.
  87. ## Use Animated Video
  88. ```text
  89. Use the animated-video skill to turn this script into an animated video.
  90. Confirm the format and show me one style frame before building the full piece.
  91. ```
  92. For the best results, run it with the strongest model you have at high effort. Short
  93. pieces take one agent; longer films can animate in parallel, with fresh agents judging
  94. the cut and a mute test before you see it.
  95. The skill needs a shell, Node.js with Remotion, FFmpeg/ffprobe, and Python 3
  96. with faster-whisper for word timings. Voiceover comes from the user or a
  97. separate tool. Music and effects come from the user's files, on-disk samples
  98. such as the video-edit sound library, or sound synthesized in code. The template holds style-neutral
  99. infrastructure only (timing, camera, still and render scripts, synthesis helpers). Optional
  100. parts from past films (a globe with a cable web, an iPhone running iMessage, synthesised sound
  101. effects) sit beside it to copy and restyle. Characters, art direction, and creative defaults are
  102. designed per project or supplied by you.
  103. For photoreal or physically detailed worlds, the skill reads its realistic-3D style pack for scale,
  104. materials, light and motion, chooses between three.js in Remotion and an optional
  105. [Blender](https://www.blender.org/) render, and gets one moving test shot accepted before the
  106. full build. For the three.js route it starts from a tested realism kit in `templates/parts/`:
  107. sky and sun with environment lighting and haze, shadows that hold still under a moving camera,
  108. seeded grass, trees and stone, frame-driven wind, and cause-driven weathering. A runnable outdoor
  109. example shot ([examples/realistic-3d](examples/realistic-3d/README.md)) renders at under half a
  110. second per 720p frame and checks that re-rendered frames are identical. It is a detailed 3D
  111. starting point that still reads as CGI, not photographic quality.
  112. Asked by video-edit (or by you) for a single animated or 3D shot inside a camera edit, it skips
  113. the story steps, works to the edit's frames and returns the clip with its sound events.
  114. ## Use Asset Library
  115. ```text
  116. Use the asset-library skill to set up a library for my video projects.
  117. Before sourcing anything for this edit, search it, and register anything another project will reuse.
  118. ```
  119. The library is one SQLite database plus your files, under one folder you choose, driven by
  120. `scripts/library.py` (Python 3, FFmpeg for probing and previews). There is no server. Media is
  121. versioned by content hash; characters, code and 3D sets are snapshotted as bundles with their
  122. files, dependencies, an example, a preview and a validation command, so a cut recorded with a
  123. version can always find what it used. When you want the record, the producing skill declares which
  124. library entries a delivered cut used, and the check confirms each has a use for that cut and version;
  125. whether an asset was worth keeping stays your call. Put the library's location and
  126. your reuse rules in `~/.asset-library/profile.md`.
  127. ## Use Video Script
  128. ```text
  129. Use the video-script skill to brainstorm ideas for my next video.
  130. Rank them by who has a stake, and give each a hook, a second sentence, and what we'll show.
  131. ```
  132. It works best with a library of your past videos and their analytics: one Markdown
  133. file per video plus an index, in the [library format](skills/video-script/references/library.md).
  134. Point the skill at it, and at your voice and pace, in `~/.video-script/profile.md`.
  135. To review a posted video, give it the insights screenshots; it reads the retention
  136. curve with `scripts/retention_curve.py` (Python 3 with Pillow and numpy) and
  137. checks the reading against the app's average watch time.
  138. ## Evaluation
  139. [Reflect's evaluation cases](skills/reflect/evals/evals.json) cover feedback, constructive pushback, unnecessary repeat checks, necessary investigation, findings that warrant no instruction changes, and keeping one project's output from becoming a default when it seeds a new skill.
  140. [Animated Video's evaluation cases](skills/animated-video/evals/evals.json) cover locking the format before building, treating a past film as evidence rather than a template, and making an explainer without a reference video.
  141. [RSI's evaluation cases](skills/rsi/evals/evals.json) cover missed skill discovery, exposed final tests, altered graders, authorized local adoption, creative judgment, and unproven improvement of the improvement process.
  142. To assess behavior, give an independent agent `SKILL.md`, a case's request and session evidence, then its feedback at the appropriate point. Keep the case's `checks` hidden until reviewing the response. These are evaluation scenarios, not an automated test suite or a guarantee of future performance.
  143. Run Video Edit's caption-helper check with Python 3:
  144. ```sh
  145. python3 skills/video-edit/scripts/test_make_captions.py
  146. ```
  147. This checks caption generation, time mapping, raw transcript preservation, and
  148. known warning/error behavior. It does not validate a Resolve installation,
  149. listening quality, visual taste, or an end-to-end video edit on your machine.
  150. Run Asset Library's check, which builds a throwaway library in a temporary folder:
  151. ```sh
  152. python3 skills/asset-library/scripts/test_library.py
  153. ```
  154. It checks ingest and duplicate detection, bundle versions and their publishing, use recording,
  155. the project check against a cut declaration, and that an older database is backed up and
  156. migrated without losing rows. It says nothing about
  157. whether the assets in your library are any good.
  158. ## Icons
  159. [Charade](icons/README.md) is a set of line icons that act out what they mean. Each one plays a short
  160. animation of its own verb when its button or link is hovered or focused: the lock unlocks, the
  161. bell swings, the trash eats a crumb. There are 203 icons in plain SVG and CSS, with no
  162. dependencies. Open `icons/index.html` from a local server to browse them.
  163. ## Contributing
  164. Keep each skill self-contained and focused on a recurring need. Include examples or evaluation cases that expose meaningful mistakes. Keep transcripts, credentials, personal project history, and machine-specific paths out of published skills. For third-party contributions, preserve attribution and confirm license compatibility.
  165. Skills stay general; personalization lives outside the repo, in each skill's `~/.<skill>/profile.md` and the files it points to. Before changing a skill, ask whether the change would be right for a stranger making their own videos. If so, write it here generically. If it is right only for you (your audience, taste, numbers, machine or accounts), put it in your profile. When it is both, split it: the general rule here, your value and the evidence behind it in your profile. Bundle only assets whose license allows redistribution, and keep the creator's own footage, likeness and personal media out.
  166. ## License
  167. [MIT](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

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