Learning & Documentation Agent Skills for Claude Desktop

Present pathway options and orchestrate place-based curriculum design from a local place, curriculum requirement, or community issue.

Anchor curriculum learning in a specific local place with connections to community, culture, and identity.

Fill a placeholder — infer the best content from surrounding context.

Explain a topic or rewrite the last response so it is extremely simple, visual, and easy to understand.

Apply when writing or editing PlantUML (.puml, .plantuml, .pu) files or when generating diagrams from text descriptions.

Use when packaging a PLDI artifact for the post-acceptance evaluation — earning the Functional, Reusable, and Available badges, archiving…

Use when turning an accepted PLDI paper into its PACMPL Issue PLDI article — de-anonymization, acmsmall journal formatting, ACM rights and…

Use when designing or auditing a PLDI evaluation — choosing defensible benchmark suites and baseline compiler configurations, measuring…

Use when positioning a PLDI paper against the SIGPLAN family and systems neighbors — stating technical deltas per cited line, covering the…

Use when interpreting PLDI's review pipeline — double-blind HotCRP reviewing by a PL-implementor PC, the February author-response window…

Use when deciding what accompanies a PLDI submission beyond the 20 text pages — full proofs, extended benchmark data, anonymized code…

Use when deciding whether a project is PLDI-shaped — implementation insight with benchmark-grade evidence — or better routed inside the…

Use when revising a PLDI draft for the venue's voice — design insight before tool name, mechanisms instead of adjectives, a running…

Use when targeting PMLA (Publications of the Modern Language Association) or deciding whether a literary- or language-studies manuscript…

Use when an author expects an artifact-evaluation or badge track at ACM PODC and needs redirecting — PODC has NO artifact track and no ACM…

Use when building the evidence for an ACM PODC paper — where "evidence" is a proof, not a benchmark.

Use when writing the related-work and positioning of an ACM PODC paper — covering the distributed-computing literature lanes…

Use when making an ACM PODC paper's result independently checkable — reproducibility for a proofs venue, not an artifact venue.

Use when reasoning about how an ACM PODC submission is evaluated — covering lightweight double-blind review, a program committee that…

Use when deciding whether a distributed-computing result belongs at ACM PODC or should be routed to DISC, SPAA, OPODIS/SIROCCO/SSS…

Use when drafting or revising the body of an ACM PODC paper — building the distributed-theory skeleton (an explicit model box, the result…