PMS Task

Create PMS tasks (bugs or features) on GitHub and sync to Google Sheets. Use when user says 'PMS Bug addition' for bugs or 'PMS Feature addition' for feature...

Security Scan

The skill's instructions would interact with a specific GitHub repo and Google Sheets but the package metadata does not declare the required CLI tools or credentials, creating an incoherent and potentially risky mismatch.

Purpose & Capability

SKILL.md's stated purpose is to create GitHub issues and update Google Sheets. The runtime instructions call out the GitHub CLI (gh) and a 'gog' CLI for Sheets and reference a specific repo (roshanasingh4/apni-pathshala-pms), two Google Sheet IDs, hard-coded assignees and reporter email. However, the skill metadata declares no required binaries, no required environment variables, and no primary credential — a mismatch: creating issues and editing Sheets requires authenticated CLI access, so the declared requirements are incomplete and inconsistent with the actual actions.

Instruction Scope

The instructions explicitly tell the agent to run commands that will create issues in a specific GitHub repo and mutate two specific Google Sheets. They also instruct to parse sheet contents (to increment task IDs) and to append/update cells. While these actions fit the described purpose, the instructions assume pre-existing authenticated CLIs and hard-code external resource identifiers and assignees, which expands the skill's effective privileges without declaring them. There is no step to prompt the user to confirm credentials or ownership of the target repo/sheets before making changes.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be downloaded or written to disk by the skill bundle itself. That lowers installation risk compared to pull-and-execute installers.

Credentials

The workflow requires access to GitHub (gh) and Google Sheets (gog) credentials or authenticated CLI sessions, but the skill declares no env vars or primary credential. It also hard-codes repository, sheet IDs, an assignee (roshanasingh4) and an assigned email ([e-mail]) — these are external account targets that the user may not intend to grant access to. The lack of declared credential requirements is disproportionate and unclear.

Persistence & Privilege

The skill is not marked always:true and does not request to modify other skills or system-wide agent settings. Autonomous invocation is allowed (platform default) but there is no indication of additional persistent privileges in the bundle itself.

What to consider before installing

This skill will run gh and gog CLI commands that create GitHub issues and edit two specific Google Sheets. Before installing, confirm: (1) you or the agent will have authenticated GitHub CLI and Google Sheets CLI access — the skill does not declare or request credentials explicitly; (2) you are OK with the skill creating issues in repo roshanasingh4/apni-pathshala-pms and assigning them to user roshanasingh4; (3) you trust updates to the two Sheet IDs listed (verify the IDs correspond to the intended documents); (4) test in a sandbox account/repo or with read-only access if possible. Ask the publisher to update the skill metadata to declare required binaries (gh, gog, jq) and the credential expectations, and to remove or parameterize hard-coded assignees and emails. These changes would reduce ambiguity and raise confidence.

PMS Task Addition (Bug & Feature)

Streamlined workflow for logging PMS bugs AND features to GitHub and Google Sheets.

Trigger

User message contains:

• "PMS Bug addition" → Creates a BUG report
• "PMS Feature addition" → Creates a FEATURE request

Workflow

1. Determine Task Type

Based on trigger phrase:

Trigger	Type	GitHub Label	Sheet Task Type
"PMS Bug addition"	Bug	bug	Issue
"PMS Feature addition"	Feature	enhancement	Feature

2. Collect Task Information

Ask the user for (if not provided):

• Title: Brief summary
• Description: What's happening (bug) or what's needed (feature)
• Reproduction Steps: (Bugs only) How to reproduce
• Expected Outcome: What should happen
• Priority: P0 (Critical) / P1 (High) / P2 (Medium) / P3 (Low)

3. Create GitHub Issue

For BUGS:

gh issue create --repo roshanasingh4/apni-pathshala-pms \
  --title "<title>" \
  --body "$(cat <<EOF
## Description
<description>

## Steps to Reproduce
1. <step 1>
2. <step 2>
3. <step 3>

## Expected Outcome
<expected outcome>

## Actual Outcome
<what actually happened>
EOF
)" \
  --label "bug,<priority>" \
  --assignee roshanasingh4

For FEATURES:

gh issue create --repo roshanasingh4/apni-pathshala-pms \
  --title "<title>" \
  --body "$(cat <<EOF
## Feature Request
<description>

## Expected Behavior
<expected outcome>

## Use Case
Why is this feature needed?
EOF
)" \
  --label "enhancement,<priority>" \
  --assignee roshanasingh4

Capture the issue URL from output for the sheet.

4. Update PMS Task Tracker Sheet

Sheet ID: 1O07SzGzQa2FwpkBE7h2SUDWZlxsUpz8DxCpyxKjRi8U Tab: Production

Column Mapping (A-K)

Col	Name	Value
A	Task ID	PMS-TSKXXX (increment from last entry)
B	Description	Issue title
C	Reporter	Tara Singh Kharwad
D	Date Submitted	DD/MM/YYYY (issue creation date)
E	Status	New
F	Task type	Issue (bug) / Feature (enhancement) / Testing
G	Priority	Critical (P0) / High (P1) / Medium (P2) / Low (P3)
H	Assigned To	[e-mail]
I	Resolution Notes	GitHub issue URL
J	Resolution Date	(empty until closed)
K	Took Help from Roshan	(leave empty - Tara fills manually)

Label to Sheet Mapping

GitHub Label	Task Type	Priority
bug	Issue	-
enhancement	Feature	-
P0	-	Critical
P1	-	High
P2	-	Medium
P3	-	Low

Get Next Task ID

gog sheets get 1O07SzGzQa2FwpkBE7h2SUDWZlxsUpz8DxCpyxKjRi8U "Production!A:A" --json | jq '.values | .[-1][0]'

Then increment the number.

Append to Sheet (BUG)

gog sheets append 1O07SzGzQa2FwpkBE7h2SUDWZlxsUpz8DxCpyxKjRi8U "Production!A:K" \
  --values-json '[["PMS-TSK-XXX","<title>","Tara Singh Kharwad","DD/MM/YYYY","New","Issue","Low","[e-mail]","<github_url>","",""]]' \
  --insert INSERT_ROWS

Append to Sheet (FEATURE)

gog sheets append 1O07SzGzQa2FwpkBE7h2SUDWZlxsUpz8DxCpyxKjRi8U "Production!A:K" \
  --values-json '[["PMS-TSK-XXX","<title>","Tara Singh Kharwad","DD/MM/YYYY","New","Feature","Low","[e-mail]","<github_url>","",""]]' \
  --insert INSERT_ROWS

5. Update Team Daily Update Sheet

Sheet ID: 1GgRgfVBrF-ReGPRmntT6Cm2BjiLzJ3JiBaC4lMfrMQs

Find row with today's date, append to Column B with format:

- PMS - <title> - <github_url>

Format for Daily Tasks

Each day's tasks are in a single cell with headings and bullet points:

- PMS - Fixed login button issue - https://github.com/...
- PMS - Added export feature - https://github.com/...

Get Today's Row

# Find row with today's date
gog sheets get 1GgRgfVBrF-ReGPRmntT6Cm2BjiLzJ3JiBaC4lMfrMQs "Sheet1!A:B" --json
# Look for today's date (DD/MM/YYYY) in Column A

Update Cell

# Append to existing content in Column B
gog sheets update 1GgRgfVBrF-ReGPRmntT6Cm2BjiLzJ3JiBaC4lMfrMQs "Sheet1!B<row>" \
  --values-json '[["<existing_content>\n- PMS - <title> - <github_url>"]]'

Priority Guide

Priority	Label	When to Use
P0	Critical	System down, data loss, security issue
P1	High	Major feature broken/needed, many users affected
P2	Medium	Feature partially working/needed, workaround exists
P3	Low	Minor issue, cosmetic, low impact

Example Usage

Bug Example

User: "PMS Bug addition - Login page crashes on mobile"

Response:

1. Detect: BUG → GitHub label: bug, Sheet type: Issue
2. Ask for details (steps, expected outcome, priority)
3. Create GitHub issue with bug template → get URL
4. Get next Task ID from sheet
5. Append to PMS Task Tracker with Task type = "Issue"
6. Update Team Daily Update sheet with new entry

Feature Example

User: "PMS Feature addition - Add dark mode support"

Response:

1. Detect: FEATURE → GitHub label: enhancement, Sheet type: Feature
2. Ask for details (description, expected behavior, use case, priority)
3. Create GitHub issue with feature template → get URL
4. Get next Task ID from sheet
5. Append to PMS Task Tracker with Task type = "Feature"
6. Update Team Daily Update sheet with new entry

Quick Reference

Trigger	GitHub Label	Sheet Task Type	Issue Template
PMS Bug addition	bug	Issue	Bug report with reproduction steps
PMS Feature addition	enhancement	Feature	Feature request with use case

Notes

• Reporter is ALWAYS "Tara Singh Kharwad"
• Assigned To is ALWAYS "[e-mail]"
• Resolution Notes = GitHub issue URL
• "Took Help from Roshan" is left empty (Tara fills manually)
• Date format: DD/MM/YYYY only
• Status starts as "New"