AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Goals

skill-kriscard-skills-goals · by kriscard

>-

No reviews yet
0 installs
44 views
0.0% view→install

Install

$ agentstack add skill-kriscard-skills-goals

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-kriscard-skills-goals)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Goals? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Goals Review

Check-in and update goal notes across quarterly, monthly, and weekly levels. Goal reviews only matter if they connect to action — this skill always ends with concrete next steps, not just status updates.

Ask, Don't Assume

Shared principle (canonical version in the vault skill): never guess, deduce, or fill gaps with assumptions about the user's notes, priorities, or intent. If you don't know — a date range, what counts as a win, which goals are active — ask. Before writing any synthesis or judgment into a note, show your draft with its source and get explicit confirmation. Missing data is not permission to invent.

Step 1 — Determine Review Level

If $ARGUMENTS is provided, use it. Otherwise ask via AskUserQuestion:

> "Which goals review would you like?" > > - Quarterly > - Monthly > - Weekly

Step 2 — Load Context (run in parallel)

# OKR dashboard
obsidian base:query path="2 - Areas/Goals/OKR Dashboard.base" format=json 2>/dev/null

# Active projects (goal alignment check)
obsidian files folder="1 - Projects/" format=json

Step 3 — Level-Specific Workflow

Weekly Review

Read this week's note:

obsidian read path="2 - Areas/Daily Ops/Weekly/M - Month YYYY/YYYY-Www.md"

Check: are this week's planned priorities covered by monthly goals? Identify any monthly goals with no weekly activity. Set next week's top 3 priorities.

Update the weekly note's "Next Week Focus" section.

Monthly Review

MONTHLY="2 - Areas/Goals/Monthly/M - $(date +'%B %Y').md"
obsidian read path="$MONTHLY" 2>/dev/null || \
  obsidian create path="$MONTHLY" template="Monthly Goals"

Check quarterly progress: which quarterly objectives is this month advancing? Flag at-risk goals — objectives with less than expected progress given the month's position in the quarter.

Update with: progress status per goal, adjustments, and next month's focus.

Quarterly Review

Read the current quarterly note:

# Note: folder name uses "Quaterly" spelling — preserve exactly
QTR_PATH="2 - Areas/Goals/Quaterly/Quaterly Goals - QN YYYY.md"
obsidian read path="$QTR_PATH" 2>/dev/null

For a mid-quarter check-in: assess progress, flag at-risk objectives, surface blockers.

For a quarter wrap + new quarter: review previous quarter outcomes (hit / partial / missed), extract learnings, then set new quarterly objectives broken into monthly milestones.

Ask via AskUserQuestion: "Is this a check-in or quarter transition?"

For new quarter setup, create the new quarterly note:

obsidian create path="2 - Areas/Goals/Quaterly/Quaterly Goals - Q YYYY.md" \
  template="Quarterly Goals"

Step 4 — Update the Goal Note

Update the relevant note with:

  • Progress status per objective
  • Adjustments to goals (if circumstances changed)
  • Next actions tied to each objective

The CLI has no patch. If the update can append to the note, use obsidian append. If it must change a specific section, ask the user: MCP obsidian_patch_content (heading-targeted) or read + create ... overwrite. Always show a preview before writing.

Gotchas

  • The quarterly folder is Quaterly (not "Quarterly") — this is a known vault typo. Match it

exactly or file creation will break.

  • Don't create a new quarterly note mid-quarter — read the existing one.
  • Don't mark a goal "missed" without asking if it should be adjusted instead. Goals can be refined;

they shouldn't just silently fail.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.