Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/dev-guide-repo-watch
Read-only workflow for sweeping the Lingtai-AI GitHub org for open issues, open PRs, and recent activity. Use this when a LingTai developer/operator asks what changed across the org, wants to monitor non-self PRs/issues, or needs an idempotent repository-health digest. This is a nested lingtai-dev-guide reference, not a top-level intrinsic skill.
Passed 13 of 17 test cases with the skill, and 5 of 17 without it.
and 14 more in the full report
11 fixed6 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
What explicit text statement must conclude any Lingtai repository sweep report?
| Checked | Without skill | With skill |
|---|---|---|
| States explicitly that no GitHub state was changed | Missed | Passed |
The instructions your model reads when the skill loads.
This nested lingtai-dev-guide reference is a read-only developer workflow for
sweeping the Lingtai-AI GitHub org. It lives here because it is
LingTai-project-specific; it should not be installed as a kernel intrinsic
capability for every agent.
Use gh from a clean shell with GitHub auth already configured.
gh repo list Lingtai-AI --limit 100 \
--json name,visibility,isArchived,pushedAt,url
gh search issues --owner Lingtai-AI --state open --limit 200 \
--json number,title,repository,state,createdAt,updatedAt,author,labels,assignees,url
gh search prs --owner Lingtai-AI --state open --limit 200 \
--json number,title,repository,state,isDraft,createdAt,updatedAt,author,labels,url
gh search prs --json does not support reviewDecision on all installed gh
versions. If review-decision status is needed, fetch it separately for a small
set of PRs with a command/API that supports that field; do not put
reviewDecision in the broad gh search prs field list unless you have verified
that local gh supports it.
For "non-self" monitoring, filter after fetching rather than hard-coding a single
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.