ProjectTelos
Project-only Telos context mapping for goals, constraints, stakeholders, decisions, dependencies, risks, and narrative reports. Use when analyzing a project, building a project context pack, mapping dependencies, writing an executive project brief, or creating a non-personal project dashboard/report.From its SKILL.md
npx -y skills add mj-deving/pai-skills --skill ProjectTelosAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.2 KB, 409 tokens by cl100k_base, as published. Nobody here has run it
Project Telos
Use this skill to build a portable, non-personal operating map for a project or organization.
This public variant intentionally excludes personal life, career, belief, and private-user memory workflows. Work only from user-provided files, repositories, notes, or public sources.
Boundaries
- Do not read private personal context directories unless the user explicitly provides them for this task.
- Do not store personal beliefs, goals, credentials, or private life context.
- Do not include secrets in generated reports.
- Treat project context as shareable by default unless the user says otherwise.
Core Model
Capture the project as:
- Purpose: mission, goals, success criteria, and non-goals.
- Actors: users, teams, stakeholders, owners, dependencies.
- Assets: repositories, docs, dashboards, datasets, services, APIs.
- Decisions: architectural choices, product calls, open questions.
- Constraints: deadlines, budgets, compliance, technical limits.
- Risks: blockers, unknowns, fragility, coordination hazards.
- Trajectory: current state, next milestones, and likely future forks.
Workflow
- Define the project boundary and intended audience.
- Inventory available evidence: docs, code, issues, PRs, diagrams, notes, and source links.
- Extract entities, decisions, dependencies, risks, and unresolved questions.
- Identify contradictions, stale assumptions, and missing owners.
- Produce a project context pack or executive brief.
- Recommend concrete follow-up tasks, owners, and validation checks.
Output Patterns
For a compact context pack:
- Project Thesis
- Current State
- Dependency Map
- Decision Log
- Risks / Unknowns
- Next Actions
For an executive report:
- Executive Summary
- Strategic Context
- Operating Model
- Progress and Blockers
- Recommendations
- Appendix: Evidence Reviewed
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.