Agent skill

Issue Grievance Tracker

by sickn33 in sickn33/agentic-awesome-skills

Grievance register: issue type, raised by or anonymous, person or team concerned, department, date raised, policy reference, severity, assignee, action taken and status.

MITAuto-check passed

Install Issue Grievance Tracker

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill issue-grievance-tracker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills issue-grievance-tracker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/issue-grievance-tracker .claude/skills/issue-grievance-tracker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
issue-grievance-tracker
GitHub stars
47k
Used in
1 other repo
Token cost
~4.1k tokens
SKILL.md length
1,485 words
Files
1
Skills in repo
1,493
Repo updated
First seen
Licence
MIT

At a glance

Grievance register: issue type, raised by or anonymous, person or team concerned, department, date raised, policy reference, severity, assignee, action taken and status.

  • Works in 5 steps: Identify intent → Ask only what is missing → Hold the internal context → …
  • Complaint handling
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Field Reference, plus 9 more sections
  • Reaches json-schema.org

What it does

Issue Grievance Tracker is an agent skill from sickn33/agentic-awesome-skills. Grievance register: issue type, raised by or anonymous, person or team concerned, department, date raised, policy reference, severity, assignee, action taken and status. Use for complaint handling.

Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Complaint handling

Example prompts

  • “/issue-grievance-tracker”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify intent
  2. Ask only what is missing
  3. Hold the internal context
  4. Recommend the smallest workflow
  5. Build only on request

What it can do on your machine

Read from SKILL.md and the folder at commit 680176d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, csv, sql, json and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • json-schema.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Issue Grievance Tracker loads about 4.1k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 1,485 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit 680176d, republished under its MIT licence (© sickn33). 1,485 words, ~4,129 tokens.

Download SKILL.mdSave it as .claude/skills/issue-grievance-tracker/SKILL.md (or your agent's skills folder).
name
issue-grievance-tracker
description
Grievance register: issue type, raised by or anonymous, person or team concerned, department, date raised, policy reference, severity, assignee, action taken and status. Use for complaint handling.
category
business
risk
safe
source
self
source_type
self
date_added
2026-09-26
author
WHOISABHISHEKADHIKARI
tags
sme, business, operations, database, csv, notion, sql, manage
source_repo
WHOISABHISHEKADHIKARI/sme-ops-system-builder

Issue & Grievance Tracker

What it is: Code of Conduct issues, internal complaints and workplace problems.

Overview

Works out the smallest useful Issue & Grievance Tracker setup for the business in front of it, then builds it only when asked. The default output is a short recommendation, not a spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on request, from one field list so they cannot drift apart.

Layer: Layer 4: Manage. Fits: Starter stage. Table code: n/a.

When to Use This Skill

  • grievance tracker
  • workplace complaint log
  • code of conduct case
  • anonymous complaint box

Also use it when the user says "code of conduct issues, internal complaints and workplace problems", or describes the same process happening in a spreadsheet, a document or someone inboxes.

Do not use it for: payroll calculation, tax filing, or legal advice. This skill produces empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

  • "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
  • "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
  • "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
  • "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

Q: Is this an anonymous complaint?

Step 2 - Ask only what is missing

Skip anything the user already answered, in any earlier message. Ask the rest one at a time, and stop as soon as the remaining answers would not change the output.

  • Type - Conduct, safety or pay? / One person or a team? / First or repeat?
  • Process - Who triages? / Investigation owner? / SLA days?
  • Privacy - Anonymous allowed? / Who can see it? / Confidentiality level?
  • Current process - How are complaints handled now? / Verbal or written? / What gets missed?
  • Outcome - What do you need? / A log, an investigation record or both?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless they ask, and it never carries a value the user did not give.

yaml
module: issue-grievance-tracker
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Type": null
  "Process": null
  "Privacy": null
  "Current process": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking
Step 4 - Recommend the smallest workflow

If an artifact was requested, build it after resolving essential missing facts. Otherwise give a short recommendation and offer the relevant artifact.

Recommended approach: Log the complaint first with a severity and an owner, then decide if a linked disciplinary case is needed.

Why this one: Grievances are missed when they arrive verbally. Capturing them with a date and a triage owner is the whole control.

Workflow: Complaint raised → Triage → Investigation → Action taken → Closure

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the requested artifacts. For machine-readable text, keep prose outside the data; for files, provide a usable link. Report material validation failures or limitations separately.

A selected Notion output is rendered by notion-manual-import, so route the Notion step there. When the user selects Notion, hand that step to @notion-manual-import: it holds the CSV, the property mapping, the import steps and the verification checklist, and it renders the Field Reference below instead of defining a table of its own. Do not restate the mapping here and do not improvise the import steps. Manual CSV and mapping outputs need no connection. For requested workspace changes, follow the shared contract: verify actual tool access and the target before writing. A user saying "connected" is not tool evidence. Never ask for a Notion password or token.

For an Excel-compatible CSV, use UTF-8 with a byte order mark so Excel opens the text correctly. A CSV is not an .xlsx workbook; create .xlsx only when the user requests a workbook. A CSV carries no types, so after it, name the columns that need a number, date or currency format applied.

csv
Issue Title,Issue Type,Raised By,Anonymous,Against (Person or Team),Department,Date Raised,Related Policy,Severity,Description,Assigned To,Investigation Notes,Action Taken,Linked Disciplinary Case,Resolution Date,Days Open,Confidential,Status,Issue ID
Client escalation after missed milestone,Conduct,Ananya Rao,FALSE,Vikram Singh,Delivery,2026-01-15,Code of Conduct,Medium,"Repeated late status updates to the client after a missed milestone, raised by the account team.",Aarav Sharma,Witness statements collected. Meeting held with both parties.,Written warning issued and a one-to-one scheduled for next week.,PIP-2026-004,2026-01-19,4,Internal,Resolved,
sql
CREATE TABLE issue_grievance_tracker (
  issue_title VARCHAR(255),
  issue_type VARCHAR(100) NOT NULL,
  raised_by VARCHAR(255),
  anonymous BOOLEAN NOT NULL,
  against_person_or_team VARCHAR(255),
  department VARCHAR(255),
  date_raised DATE NOT NULL,
  related_policy VARCHAR(255),
  severity VARCHAR(100) NOT NULL,
  description TEXT,
  assigned_to VARCHAR(255),
  investigation_notes TEXT,
  action_taken VARCHAR(255),
  linked_disciplinary_case VARCHAR(255),  -- relation -> target record
  resolution_date DATE,
  days_open NUMERIC NOT NULL,
  confidential VARCHAR(100) NOT NULL,
  status VARCHAR(100) NOT NULL,
  issue_id SERIAL PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_issue_grievance_tracker_status ON issue_grievance_tracker (status);
json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Issue & Grievance Tracker",
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "Issue Title": {
      "type": "string"
    },
    "Issue Type": {
      "type": "string"
    },
    "Raised By": {
      "type": "string"
    },
    "Anonymous": {
      "type": "boolean"
    },
    "Against (Person or Team)": {
      "type": "string"
    },
    "Department": {
      "type": "string"
    },
    "Date Raised": {
      "type": "string",
      "format": "date"
    },
    "Related Policy": {
      "type": "string"
    },
    "Severity": {
      "type": "string"
    },
    "Description": {
      "type": "string"
    },
    "Assigned To": {
      "type": "string"
    },
    "Investigation Notes": {
      "type": "string"
    },
    "Action Taken": {
      "type": "string"
    },
    "Linked Disciplinary Case": {
      "type": "string"
    },
    "Resolution Date": {
      "type": "string",
      "format": "date"
    },
    "Days Open": {
      "type": "number"
    },
    "Confidential": {
      "type": "string"
    },
    "Status": {
      "type": "string"
    },
    "Issue ID": {
      "type": "integer"
    }
  },
  "required": [
    "Issue Type",
    "Date Raised",
    "Severity",
    "Days Open",
    "Confidential",
    "Status"
  ]
}
markdown
| CSV column | Notion property | Set after import |
|---|---|---|
| Issue Title | Title | Use as the database title |
| Issue Type | Select (add options after import) | Convert to Select, add options: "Conduct", "Harassment", "Discrimination", "Safety", "Pay", "Workplace", "Other" |
| Raised By | Text | Leave as Text |
| Anonymous | Checkbox | Convert to Checkbox |
| Against (Person or Team) | Text | Leave as Text |
| Department | Text | Leave as Text |
| Date Raised | Date | Convert to Date |
| Related Policy | Text | Leave as Text |
| Severity | Select (add options after import) | Convert to Select, add options: "Low", "Medium", "High", "Critical" |
| Description | Text | Leave as Text |
| Assigned To | Text | Leave as Text |
| Investigation Notes | Text | Leave as Text |
| Action Taken | Text | Leave as Text |
| Linked Disciplinary Case | Relation (link to the target database) | Convert to Relation, link to the target database |
| Resolution Date | Date | Convert to Date |
| Days Open | Number | Convert to Number |
| Confidential | Select (add options after import) | Convert to Select, add options: "Public", "Internal", "Restricted", "Highly Restricted" |
| Status | Select (add options after import) | Convert to Select, add options: "Logged", "Under Review", "Investigating", "Resolved", "Escalated", "Closed" |
| Issue ID | Text (preserve source ID) | Keep imported IDs as Text; optionally add a separate Unique ID property |

The rows above are documentation examples only. Emit empty templates unless the user explicitly requests examples. Money stays currency, dates stay date, and anything pointing at another table stays relation.

Field Reference

Resolution Date may be absent before the relevant lifecycle stage or when no verified source exists. Do not invent values to satisfy a schema.

#FieldTypeSQLJSON SchemaNotionCSV example
1Issue TitletextVARCHAR(255)stringTextClient escalation after missed milestone
2Issue TypeselectVARCHAR(100)stringSelect (add options after import)Conduct
3Raised BytextVARCHAR(255)stringTextAnanya Rao
4AnonymouscheckboxBOOLEANbooleanCheckboxFALSE
5Against (Person or Team)textVARCHAR(255)stringTextVikram Singh
6DepartmenttextVARCHAR(255)stringTextDelivery
7Date RaiseddateDATEstring, format: dateDate2026-01-15
8Related PolicytextVARCHAR(255)stringTextCode of Conduct
9SeverityselectVARCHAR(100)stringSelect (add options after import)Medium
10Descriptionlong_textTEXTstringTextRepeated late status updates to the client after a missed milestone, raised by the account team.
11Assigned TotextVARCHAR(255)stringTextAarav Sharma
12Investigation Noteslong_textTEXTstringTextWitness statements collected. Meeting held with both parties.
13Action TakentextVARCHAR(255)stringTextWritten warning issued and a one-to-one scheduled for next week.
14Linked Disciplinary CaserelationVARCHAR(255)stringRelation (link to the target database)PIP-2026-004
15Resolution DatedateDATEstring, format: dateDate2026-01-19
16Days OpennumberNUMERICnumberNumber4
17ConfidentialselectVARCHAR(100)stringSelect (add options after import)Internal
18StatusselectVARCHAR(100)stringSelect (add options after import)Resolved
19Issue IDidSERIAL PRIMARY KEYintegerText (preserve source ID)(blank)
Show full SKILL.md (493 more words)Show less

Select Options

Issue Type

Conduct | Harassment | Discrimination | Safety | Pay | Workplace | Other

Severity

Low | Medium | High | Critical

Confidential

Public | Internal | Restricted | Highly Restricted

Status

Logged | Under Review | Investigating | Resolved | Escalated | Closed

Relations

Link fields: Linked Disciplinary Case

Examples

Prompt

A complaint came in verbally and we handled it without a record.

Context first - one question per message, nothing already answered:

Q: Anonymous? A: Yes, it must be.

Q: Who investigates? A: HR.

Q: SLA days? A: Two days to triage.

Recommended next step - offered, not built:

Log the complaint first with a severity and an owner, then decide if a linked disciplinary case is needed.

Workflow: Complaint raised → Triage → Investigation → Action taken → Closure

Want the CSV, SQL, JSON Schema and Notion mapping for this?

Best Practices

  • Build when requested; recommend and offer a build for advice-only requests.
  • One question per message. A batched intake reads as a form and gets guessed at.
  • Keep display names identical across CSV and JSON; document normalized SQL identifiers.
  • Use relation for anything that points at another table, text only for free text.
  • Money fields are currency, never text. Dates are date, never free text.
  • If the user requests an example row, keep it obviously fake so nobody imports it as real data.

Limitations

  • Empty template only. It does not compute payroll, tax, leave balances or KPIs.
  • Notion relations need both databases imported before the link column resolves.
  • Select options are a starting set. Rename them to match how the business talks.
  • No automation, reminders or sync. Those need the integration layer.
  • Does not investigate, adjudicate or notify anyone. It records the process.
  • Legal, tax and HR review is still required before this drives real decisions.

Security & Safety Notes

  • Never fill in real names, salaries, medical or banking data. Placeholders only.
  • Label example rows as synthetic, and keep bank details masked.
  • Local reads, generation commands, and validation are part of a requested artifact build. External writes, messages, provisioning, and publication require authorization for that action and target; existing explicit authorization does not need to be repeated.
  • If sensitive data is supplied, avoid repeating unnecessary identifiers. Use only what the requested review needs; keep generated templates empty. Do not claim deletion from the conversation or service storage.
  • Privacy, legal and disciplinary cases need a qualified human reviewer before anything is acted on.

Common Pitfalls

  • Problem: a static mapping is described as a completed workspace build. Solution: deliver manual mappings without a connection; claim a live change only after the authorized tool operation succeeds.
  • Problem: asked all six questions in one message. Solution: ask one, wait, and drop any the first answer already covered.
  • Problem: built a full system when one table was asked for. Solution: build what was requested; mention the parent skill separately.
  • Problem: all four artifacts drift apart. Solution: derive all four from the field list in this file, never by hand.
  • Problem: Notion import shows every column as Text. Solution: that is expected. Apply the property mapping table once, after import.

Reusable Prompt

I want to set up code of conduct issues, internal complaints and workplace problems for my company.
Ask me one short question at a time, and only about what I have not already told you.
Then recommend the smallest setup that fits, and wait for me to ask before you build it.
When I ask, output CSV, SQL DDL, JSON Schema, a Notion property mapping or an Excel workbook. Data only.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/issue-grievance-tracker of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit 680176d

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Issue Grievance Tracker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Issue Grievance Tracker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Issue Grievance Tracker this skillsickn33/agentic-awesome-skills47k1 repos~4.1kAutomated safety check: PassMIT
Agent Issue Trackerruvnet/ruflo74k2 repos~2.4kAutomated safety check: PassMIT
Iot Registerruvnet/ruflo74k—~263Automated safety check: PassMIT
Raisely AutomationComposioHQ/awesome-claude-skills77k3 repos~730Automated safety check: PassNone
Has AnonymizerLeoYeAI/openclaw-master-skills2.2k—~4.5kAutomated safety check: PassMIT
Tc Trackeralirezarezvani/claude-skills28k—~2.6kAutomated safety check: PassMIT

Similar skills

  • Agent skill for issue-tracker - invoke with $agent-issue-tracker

    74k GitHub starsUsed in 2 repos~2.4k tokens
    DevelopmentAuto-check passed
  • Iot Register

    ruvnet/ruflo

    Register a Cognitum Seed device by endpoint and establish agent bridge

    74k GitHub stars~263 tokensUpdated today
    Auto-check passed
  • Raisely Automation

    ComposioHQ/awesome-claude-skills

    Automate Raisely tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~730 tokens
    Productivity & AutomationAuto-check passed
  • Has Anonymizer

    LeoYeAI/openclaw-master-skills

    HaS (Hide and Seek) on-device text and image anonymization. An agent skill from LeoYeAI/openclaw-master-skills.

    2.2k GitHub stars~4.5k tokensUpdated 2 mo ago
    Auto-check passed
  • Tc Tracker

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions.

    28k GitHub stars~2.6k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Contract Renewal Tracker

    anthropics/claude-for-legal

    Official

    Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.

    9.6k GitHub starsUsed in 2 repos~3.1k tokens
    Legal & ComplianceAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,493 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Issue Grievance Tracker

What does Issue Grievance Tracker do?

Grievance register: issue type, raised by or anonymous, person or team concerned, department, date raised, policy reference, severity, assignee, action taken and status. Issue Grievance Tracker is an agent skill from sickn33/agentic-awesome-skills. Grievance register: issue type, raised by or anonymous, person or team concerned, department, date raised, policy reference, severity, assignee, action taken and status.

When should I use Issue Grievance Tracker?

Issue Grievance Tracker fits situations like: complaint handling.

How do I install Issue Grievance Tracker in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill issue-grievance-tracker -a claude-code`. Or copy the skill folder (skills/issue-grievance-tracker in sickn33/agentic-awesome-skills) into .claude/skills/issue-grievance-tracker in your project. Claude Code loads it when a task matches its description.

How do I install Issue Grievance Tracker in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill issue-grievance-tracker -a codex`. Or copy the skill folder (skills/issue-grievance-tracker in sickn33/agentic-awesome-skills) into .agents/skills/issue-grievance-tracker in your project. Codex loads it when a task matches its description.

Can I use Issue Grievance Tracker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill issue-grievance-tracker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-grievance-tracker, .gemini/skills/issue-grievance-tracker, .github/skills/issue-grievance-tracker and .opencode/skills/issue-grievance-tracker in your project.

What does Issue Grievance Tracker need to run?

SKILL.md names no scripts, command-line tools or credentials: Issue Grievance Tracker is instructions for the agent only.

Does Issue Grievance Tracker access the network?

SKILL.md names 1 domain. In commands or code: json-schema.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Issue Grievance Tracker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Issue Grievance Tracker use?

Issue Grievance Tracker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Issue Grievance Tracker use?

About 4.1k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Issue Grievance Tracker?

Skills that share tags, products or a category with Issue Grievance Tracker: Agent Issue Tracker (ruvnet/ruflo, 74k stars), Iot Register (ruvnet/ruflo, 74k stars), Raisely Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Has Anonymizer (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue Grievance Tracker?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,379 GitHub stars. The repository holds 1,493 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.