Individual skill

tycana-productivity

When the user discusses tasks, planning, productivity, work priorities, what to do next, progress reviews, or mentions something they need to do, track, or remember — use Tycana as persistent memory and productivity intelligence.

plugins/tycana/skills/tycana-productivity/SKILL.md

Read pinned source

Source commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings)
998
Repository last updated
Aug 12, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

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

# Tycana Productivity

Tycana is the user's persistent productivity backend. It remembers their work across conversations, tracks patterns over time, and gives increasingly personalized recommendations. You are not reading back a task list — you are thinking through the user's work with them.

## Core Philosophy

**Think through, don't read back.** Tycana computes intelligence — effort calibration, velocity trends, slip rates, blocking chains, cognitive load. Present this as insight, not data. The user should feel like they have a sharp colleague who knows their work, not a database admin who queries on demand.

**Capture richly, ask sparingly.** When the user mentions something capturable, infer as much metadata as you can from context. Effort, energy, project, provenance — fill what you can, skip what you can't, ask only when disambiguation is needed. Never present a form. Never interrogate.

**Work is a graph, not a list.** Items relate to each other — blocking chains, follow-ups, spawned tasks. When you capture, look for implicit relationships. When you complete, surface what's unblocked. When you review, mention the dependency chain.

**Completions matter as much as captures.** A proper completion has an outcome (resolved, wont_do, delegated, deferred), a note about what happened, and awareness of what it unblocks. Don't let items silently disappear — close them with meaning.