daily-JIRA
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Daily JIRA companion for the Sentient Workforce project (SMTC). Seven sub-commands: TEAM ISSUES (open issues grouped by assignee and status), SPRINT (current sprint board with progress and blockers), STORIES BY EPIC (stories grouped under each epic with progress bars), SUBTASKS (sub-tasks under a specific story), ISSUE DETAIL (full detail card for any issue), CREATE (guided issue creation), and UPDATE (transition status, add comments, edit fields). Use whenever the user says "team issues", "what's the team working on", "show the sprint", "sprint board", "stories by epic", "epic breakdown", "subtasks for", "issue detail", "show me SMTC-", "what's the status of", "create a jira issue", "log a bug", "new story", "update issue", "transition", "add a comment to", "close issue", "move to done", or any JIRA-related request for Sentient Workforce.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- change-headingsSkill
- customer-briefSkill
- daily-calendarsSkill
- daily-emailsSkill
- daily-filesSkill
- daily-journalsSkill
- daily-knowledgeSkill
- daily-plansSkill
- daily-workSkill
- list-filesSkill
- new-presentationSkill
- new-productSkill
- new-proposalSkill
- new-quotationSkill
- news-articles-renameSkill
- news-snapshotSkill
- presentation-outlineSkill
- project-pulse-briefSkill
- prospect-briefSkill
- reverse-dateSkill
- reverse-monthSkill
- sentient-brand-guidelinesSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
29 rules. About 0 are common, 19 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈19
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.