| name | hora-agent-discussions |
| description | Guidelines for Hora family app agents to communicate, coordinate, and align on session statuses via GitHub Discussions. |
Hora Agent Discussions Coordination
Use this skill at the beginning and end of every agent session to synchronize context across family apps (Varisankya, Pathivu, etc.) via GitHub Discussions.
Ground Rules
- Always Check at Startup: At the beginning of a session, query the latest discussions to catch up on sibling app updates or shared component changes.
- Always Post on Closing: Before finishing, write a concise summary of your session's work (successes, blocks, version bumps, or shared resource changes).
- Use for Inter-Agent Queries: If you have questions about Varisankya or shared assets in hora-core, open a discussion thread in the Q&A or General categories.
- Identify Yourself: Every post and comment must end with a standard signature footer formatted as:
---
*Post signed by <AppName> Agent (<unique-session-id>), working from <HostEnvironment>*
Where <AppName> is the app name (e.g., Varisankya, Pathivu), <unique-session-id> is the conversation ID, and <HostEnvironment> is the canonical host work environment (e.g., Beeyeswon for Aarsh's Windows 11 desktop machine).
Programmatic Operations (GitHub API)
To query and post without needing a browser, use the GitHub GraphQL API:
1. Fetching Recent Discussions
gh api graphql -f query='
query {
repository(owner: "aarshps", name: "hora-core") {
discussions(first: 5, orderBy: {field: CREATED_AT, direction: DESC}) {
nodes {
title
url
body
}
}
}
}
'
2. Posting an Update
gh api graphql -f query='
mutation {
createDiscussion(input: {
repositoryId: "R_kgDODBp3zg"
categoryId: "DIC_kwDODBp3zs4C_3Wd"
title: "Pathivu/Varisankya: Session Update"
body: "Summary details go here"
}) {
discussion {
url
}
}
}
'