Guide · Agent skill
How to use the 360 Feedback System agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The 360 Feedback System is an agent skill that helps you set up a 360-degree or peer feedback process with a clean record structure. It is aimed at HR and people-ops staff, small business owners tracking feedback in spreadsheets or email, and team leads running feedback on projects, customers or teams. After this guide you will know what the skill does, how to install it, how to ask for it, and what outputs you can request.
360 Feedback Systemsickn33/agentic-awesome-skills · MIT Download the skill Quick start
- 1Download the ZIP. Download the skill ZIP from this page.
- 2Unzip into a skills folder. Unzip into ~/.claude/skills/ for all projects, or into a project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.
- 4Describe your feedback process. Ask in plain language, for example that you want to set up a 360 review cycle, and say how feedback is handled today.
- 5Answer the targeted questions. Reply to the questions one at a time. Say Unknown if you do not know an answer.
- 6Review the recommendation. Check the suggested workflow and the fields that were confirmed before requesting any output.
- 7Request the template format. Ask for CSV, SQL, JSON Schema or a Notion mapping to receive empty templates derived from the confirmed fields.
What the 360 Feedback System skill makes the agent do
The skill records one feedback response per row. Before building anything, the agent asks a few targeted questions about how your feedback process works, then recommends the simplest workflow and data structure that fits.
It only adds fields you actually confirm, such as reviewer, due date or score. Anything you do not know is recorded as Unknown rather than guessed. On request it produces empty templates in CSV, SQL, JSON Schema or Notion mapping format, all derived from one shared field list so the formats stay consistent.
- Default output is a short recommendation, not a spreadsheet.
- Templates are empty by default; the single example row contains placeholder values only.
- Scoring is kept as configuration, not as a column on each response row.
- The skill does not automate payroll, tax, legal or employment-decision work.
Install the 360 Feedback System skill
Download the skill ZIP from this page. Then choose one of two routes.
For Claude Code, unzip the file into ~/.claude/skills/ to make it available across your projects, or into a project's .claude/skills/ folder to limit it to that project.
In the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills instead.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
What the skill needs and what it touches
The skill lists no requirements. It runs no scripts and uses no network access. The package contains a single file, SKILL.md, which holds all of its instructions.
Manual CSV and mapping outputs need no connection to any tool. If you ask it to write to a Notion workspace, it first checks that it actually has tool access and the target before writing, and it never asks for a Notion password or token.
- Requirements: none listed
- Runs scripts: no
- Uses network: no
- Files: SKILL.md
How to trigger the skill with natural requests
You do not need a special command. Describe your situation in plain language. The skill responds to requests about 360 feedback, feedback systems, peer review tools and 360-degree feedback trackers, and to descriptions of the same process running in a spreadsheet, a document or an inbox.
The agent picks an intent from your request. If you only want advice, it answers and offers a build only if useful. If you say set up or build, it moves on to asking the questions it still needs.
- "Help me set up a 360 review cycle for my team. We track everything in a spreadsheet now."
- "Give me the CSV template for our peer feedback process."
- "Is our current peer review tracker structured right?"
- "Export the confirmed feedback fields as SQL DDL."
Examples of a typical session
Expect a few short questions, asked one at a time. The agent skips anything you have already answered. Vague replies such as yes, maybe or fine are not accepted as answers to multiple-choice questions; the agent asks again as an explicit choice.
For example, if you reply maybe when asked whether feedback is identified or anonymous, the agent will ask you to choose between the two. Partial answers are kept, and the rest is recorded as Unknown.
- Feedback Subject stays a generic label, so you can record a person, project, customer or team.
- Scoring is labelled Unknown until its scale, weights and missing-score rules are decided.
- An overall score is not calculated until all scoring inputs are resolved.
Tips for getting useful output
Tell the agent how your process actually runs: how feedback is collected, reviewed and followed up. The workflow it recommends is built from that description, and it will not assume a review role or an analysis tool you do not use.
Ask only for the formats you need. The skill generates every requested format from the same field list in one pass, so requesting CSV and SQL together keeps them in agreement.
Do not expect analytics. The skill produces templates and recommendations, not scoring or analysis of real feedback data.
- Describe your current process, even if it is messy.
- Confirm fields explicitly; unconfirmed fields will not be added.
- Request only the artifacts you will use.
What people use it for
- Setting up a 360 review cycle for a people-ops team that currently tracks feedback in email.
- Moving a small business's peer feedback from a spreadsheet into a cleaner, consistent structure.
- Creating an empty CSV template for a team lead running project or customer feedback.
- Producing SQL DDL or a JSON Schema from the same confirmed field list for a developer building a feedback tool.
- Checking whether an existing feedback tracker's structure makes sense.
Frequently asked questions
How do I install the 360 Feedback System agent skill?
Download the skill ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
Does the 360 Feedback System skill have any requirements?
The skill lists no requirements. It runs no scripts and uses no network access, and its package contains only SKILL.md. Manual CSV and mapping outputs need no connection to any tool.
Is the 360 Feedback System skill free?
The source lists the licence as MIT. It does not state pricing, so check the directory page for any details beyond the licence.
Can the skill analyse or score my real feedback data?
No. The skill produces templates and recommendations rather than analytics. It keeps scoring as configuration and does not calculate an overall figure until all scoring inputs are resolved.
Can I use it for payroll or employment decisions?
No. The skill explicitly declines payroll, tax, legal and employment-decision work. It will still help with the feedback setup in the same request.
What should I do if the skill asks questions I cannot answer?
Reply with Unknown. The skill records unanswered items as Unknown rather than guessing, and it will not re-ask a question you have already marked that way.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you run 360 or peer feedback cycles and want a clear, consistent record structure in CSV, SQL, JSON Schema or Notion without inventing fields you do not need. Pick something else if you want automated analysis or scoring of real feedback, or if your work involves payroll, tax, legal or employment decisions.
Download the skill