Search
Obsidian · By RafaelGB
Skills
Sort:BestMost starsTrending todayTrending this weekTrending this monthNewestRecently updatedName
| # | Skill | Repository | Stars | Used in | Tokens | Auto-check | Licence | Updated |
|---|---|---|---|---|---|---|---|---|
| 1 | Scaffold a new ZettelFlow action following the project's 4-file convention (Action / Component / Settings / SettingsReader), register it, and document it. | RafaelGB/ | 175 | — | ~1.1k | Automated safety check: Pass | MIT | yesterday |
| 2 | Audit ZettelFlow against the official Obsidian plugin guidelines and the Community-hub automated review / quality score. | RafaelGB/ | 175 | — | ~1.6k | Automated safety check: Pass | MIT | yesterday |
| 3 | 3.Release Cut a compliant ZettelFlow plugin release — version bump, versions.json, build, tag, and a GitHub Release whose notes follow the house format. | RafaelGB/ | 175 | — | ~1.4k | Automated safety check: Pass | MIT | yesterday |
| 4 | 4.Specify Stage 1 of the SDD pipeline — write a ZettelFlow spec into a GitHub issue body (problem, value, functional requirements, testable acceptance criteria, capability disclosure, out-of-scope). | RafaelGB/ | 175 | — | ~759 | Automated safety check: Pass | MIT | yesterday |
| 5 | 5.Sdd The Spec-Driven Development pipeline for ZettelFlow — the end-to-end flow (constitution → specify → plan → tasks → implement → verify) and which skill/agent owns each stage. | RafaelGB/ | 175 | — | ~842 | Automated safety check: Pass | MIT | yesterday |
| 6 | 6.TDD The test-driven development workflow for ZettelFlow — write a failing test first, run jest, use the Obsidian mock and the bare-specifier alias mappings, and know which code is unit-testable. | RafaelGB/ | 175 | — | ~724 | Automated safety check: Pass | MIT | yesterday |
| 7 | Stage 4 of the SDD pipeline — execute a ZettelFlow task checklist (in a GitHub issue comment) test-first (red → green → refactor), one commit per advance, keeping npm run verify green and CI green… | RafaelGB/ | 175 | — | ~1.7k | Automated safety check: Pass | MIT | yesterday |
| 8 | 8.Plan Stage 2 of the SDD pipeline — turn a ZettelFlow spec (in the GitHub issue body) into a technical plan posted as an issue comment (approach, files by layer, Obsidian score-rule impact, test strategy… | RafaelGB/ | 175 | — | ~651 | Automated safety check: Pass | MIT | yesterday |
| 9 | 9.Tasks Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment. | RafaelGB/ | 175 | — | ~573 | Automated safety check: Pass | MIT | yesterday |
