Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Start Week

ASecurity

Opens the calendar week with themes, outcomes, and carryover from last week. Use when the user says /start-week, start of week, weekly planning, or Monday kickoff.

10 stars
0 votes
0 copies
0 views
Added 10/6/2026
documentationgo

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add tomzx/agents --skill start-week --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Start Week?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Start Week
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tomzx-start-week/badge)](https://www.skillsdirectory.com/skills/tomzx-start-week)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: start-week
description: Opens the calendar week with themes, outcomes, and carryover from last week. Use when the user says /start-week, start of week, weekly planning, or Monday kickoff.
---

BASE_DIR=!`~/.agents/scripts/get-env NOTES_DIR`
TODAY=!`date +%Y-%m-%d`
YEAR=!`date +%Y`
WEEK=!`date +%V`

# Start Week

Sets intent for the ISO week: a small number of outcomes, how collaboration fits, and what to finish or drop from last week.

## Prerequisites

- `NOTES_DIR` set (via `~/.agents/scripts/get-env NOTES_DIR`)
- Optional: `{BASE_DIR}/goals.md`, `{BASE_DIR}/team-goals.md`
- Optional: `{BASE_DIR}/{YEAR}/weekly/{WEEK}/action-items.md` (if end-of-week-summary already ran this week)
- Optional: previous week's `{BASE_DIR}/{YEAR}/weekly/<prev>/review.md` or `action-items.md` for carryover

## Steps

### 1. Resolve week context

Use ISO week `{WEEK}` and year `{YEAR}`. If today is early in the week, treat "last week" as the previous ISO week (handle year boundary by checking weekly folders under `{BASE_DIR}/{YEAR}/weekly/`).

### 2. Gather context

Read if they exist:

- Prior week `review.md` or `action-items.md` under `{BASE_DIR}/{YEAR}/weekly/`
- `{BASE_DIR}/goals.md` and `{BASE_DIR}/team-goals.md`
- This week's `action-items.md` if it already exists

### 3. Synthesize (in chat unless the user asks for a file)

Deliver:

- **Theme** (one line for the week)
- **Top 3 outcomes** (measurable or clearly done or not done)
- **Carryover** (explicitly scheduled or explicitly dropped)
- **Collaboration** (who to sync with, what decisions are waiting)
- **Risks** (capacity, dependencies, recurring meetings to trim)

### 4. Optional file output

If the user wants it persisted, write `{BASE_DIR}/{YEAR}/weekly/{WEEK}/plan.md`:

```markdown
---
week: {WEEK}
year: {YEAR}
date: {TODAY}
---

# Week plan

## Theme
## Top 3 outcomes
## Carryover from last week
## Collaboration and decisions
## Risks and constraints
```

## Relationship to other skills

- **end-of-week-summary** and **end-of-week-review** populate reflection and action items; start-week should reference them when present.
- Do not run the Slack or colleague pipelines from end-of-week-summary here unless the user explicitly asks for a weekly digest.

Attribution

tomzxtomzx
View sourceSee grades on GitHubMore from tomzx →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

Architecture Diagram Creator

Create comprehensive HTML architecture diagrams with data flows, business context, and system architecture.

6661 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in W...

1798860 votes
View all in documentation →