chronicle-project-tracker
Track Chronicle Project Milestones
Development work can become hard to connect to milestones, sessions, and roadmap priorities. This skill uses Chronicle MCP tools and CLI workflows to track progress and next steps.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "chronicle-project-tracker" from https://skillstore.io/skills/chandlerhardy-chronicle-project-tracker.md and its manifest at https://skillstore.io/api/skills/chandlerhardy-chronicle-project-tracker/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "chronicle-project-tracker". What should I work on next?
Expected outcome:
A ranked roadmap summary with active milestones, high priority planned work, pending next steps, and recent completions.
Using "chronicle-project-tracker". What did I accomplish this week?
Expected outcome:
A progress report that groups completed milestones with linked sessions, commits, time spent, and key files changed.
Using "chronicle-project-tracker". Help me start a new API milestone.
Expected outcome:
A suggested milestone title, description, priority, tags, and a short list of next steps to add in Chronicle.
Security Audit
SafeThe static alerts are false positives caused by Markdown backticks, code fences, Chronicle CLI examples, and MCP tool names. I found no prompt injection attempt, hidden exfiltration intent, or malicious system reconnaissance in SKILL.md. Users should still review optional Chronicle CLI updates because they can change local project tracking state.
Risk Factors
⚙️ External commands (86)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/chandlerhardy-chronicle-project-tracker/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/chandlerhardy-chronicle-project-tracker?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/chandlerhardy-chronicle-project-tracker?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/chandlerhardy-chronicle-project-tracker/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/chandlerhardy-chronicle-project-tracker.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
ChandlerHardy. (2026). chronicle-project-tracker security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/chandlerhardy-chronicle-project-tracker/audits/8BibTeX citation
@techreport{chandlerhardy-chandlerhardy-chronicle-project-tracker-2026,
author = {ChandlerHardy},
title = {chronicle-project-tracker security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/chandlerhardy-chronicle-project-tracker/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "chronicle-project-tracker security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "ChandlerHardy"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/chandlerhardy-chronicle-project-tracker/audits/8"
identifiers:
- type: other
value: "skillstore:chandlerhardy-chronicle-project-tracker:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan Feature Work
Review the existing roadmap, create a milestone, and break the feature into prioritized next steps.
Prepare Progress Reports
Summarize completed milestones, linked sessions, commits, and remaining work for a reporting period.
Connect Sessions to Roadmap Items
Find the active milestone, link a development session, and mark completed next steps.
Try These Prompts
Show the Chronicle roadmap for the next 7 days and group it by active work, planned work, and next steps.
Check the current Chronicle roadmap for duplicate work, then draft a milestone and three next steps for this feature: [feature].
Find the most recent Chronicle session, identify the active milestone, and prepare the steps to link them safely.
Create a weekly Chronicle progress report from completed milestones, linked sessions, commits, durations, and pending next steps.
Best Practices
- Review the roadmap before creating new milestones to avoid duplicate work.
- Link sessions while work is fresh so reports stay accurate.
- Use consistent milestone types, priorities, and tags for reliable filtering.
Avoid
- Creating milestones without checking existing active or planned work.
- Marking milestones complete before all required next steps are resolved.
- Using vague tags or priorities that make roadmap ordering unclear.
Frequently Asked Questions
What does this skill track?
Does it require MCP tools?
Can it create milestones automatically?
Can it update documentation files?
Is this a general project management skill?
How should commands be handled?
Developer Details
Author
ChandlerHardyLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/ChandlerHardy/chronicle/tree/main/chronicle-skills/chronicle-project-trackerRef
dd4a3ef9f20ddf38830950b4bb713df96b431fd6
Maintenance freshness
7/18/2026
Usage
7 downloads · 280 views
File structure
📄 SKILL.md