Individual skill
journal-entry-prep
Create or review journal entry prep deliverables with traceable assumptions, decision criteria, ownership, and risk controls. Use when the user asks for journal entry prep planning or analysis.
marketing/journal-entry-prep/SKILL.md
Source commit cbab58188611e626ccaf54ac346b437d12ea4729
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 207
- Repository last updated
- Sep 26, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- codex-skills Repository topic
- deepseek Repository topic
- deepseek-harness Repository topic
- marketing-automation Repository topic
- research-tools Repository topic
- claude-code Repository topic
- cursor-ai Repository topic
- gemini-cli Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Journal Entry Prep
Use this Skill to produce a bounded, verifiable Journal Entry Prep outcome. Preserve the user's chosen stack, source material, and authorization boundaries.
Read [the SandBase API map](references/sandbase-api-map.md) only when the task genuinely needs an external data source or generative model.
## Workflow
1. Inspect the available files, runtime, versions, inputs, and existing conventions before deciding what to change.
2. Restate the requested outcome, constraints, acceptance checks, and any assumption that could change the result.
3. Produce the smallest complete implementation, analysis, or artifact that satisfies those checks.
4. Verify the real output with appropriate tests, previews, calculations, or source comparison; do not infer success from file creation alone.
5. Return the deliverable, evidence of validation, material assumptions, and unresolved limitations.
