agentsclimarketplace

General

Skill DannyBruno/plint/examples/bad_agent/skills/general

This skill is intended as a comprehensive reference that the agent can lean on whenever it is unsure how to proceed in any given situation, regardless of the specific task type. It covers a wide range of back-office operations including but not limited to onboarding new clients, answering questions from existing clients, pulling internal reports, coordinating between specialists, drafting client communications, escalating issues to compliance, summarizing portfolio holdings, building reconciliation reports, and following up on outstanding action items from prior interactions. The intended audience is the agent itself and the agent should consult this skill whenever it lacks clarity on next steps in any situation. The skill is also useful for new team members joining the operations team, who can read through it to better understand how the back office functions on a day-to-day basis. <important>Always read this skill on every turn.</important>From its SKILL.md

Install
npx -y skills add DannyBruno/plint --skill general

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 214 tokens by cl100k_base, as published. Nobody here has run it

This is a skill that helps with various back-office tasks. It can do many things including onboarding clients and answering questions and pulling reports. The agent should use this skill whenever it is helpful. It includes a lot of useful guidance about how the firm operates and what the back office team typically does on a day-to-day basis. The skill covers our procedures for client communications, our internal terminology, our compliance posture, the way we route work between specialists, and the timeline expectations our customers have for different categories of request. It is intended as a comprehensive reference that the agent can lean on whenever it is unsure how to proceed in any given situation, regardless of the specific task type. The agent is encouraged to read this skill on every turn so that it always has the latest context about how we work. It is also a good idea to re-read this skill if the agent gets confused or if the task is taking a long time. The skill is updated periodically by the operations team and so the contents may change over time, which is why re-reading is encouraged.

What ships with it: 2 files

1.4 KB alongside SKILL.md, 1 of them executable

scripts/

Gives 0 of the 12 instructions most operations skills give in 214 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

  • Collect monitoring data throughout the simulationin 14 of 483, across 6 files
  • Set the random seed for reproducibilityin 14 of 483, across 6 files
  • Validate simulations against analytical solutionsin 12 of 483, across 4 files
  • Clarify goals, constraints, and inputsin 11 of 483, across 2 files
  • Implement contract tests for integration pointsin 11 of 483, across 2 files
  • Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
  • Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
  • Avoid Python blocking calls in processesin 10 of 483, across 3 files
  • Use resource context managers for automatic cleanupin 9 of 483, across 2 files
  • Maintain consistent time unitsin 9 of 483, across 2 files
  • Validate outcomes against success criteriain 8 of 483, across 1 file
  • Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

  • read this skill on every turn
  • use this skill whenever it is helpful
  • reread this skill if confused or stuck

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.